搜索技能.../

Git Conventions | Skills Pool

技能档案

Git Conventions

Git conventions for branches, commits, and PRs. Use when creating branches, writing commit messages, opening pull requests, or deciding on PR base branch. Also use when the user asks about branch naming, commit format, PR title style, or how to reference JIRA tickets in git operations. Consult proactively before any git commit, push, branch creation, or PR operation.

ag-grid15,227 星标2026年3月25日

职业
分类: Git 工作流

技能内容

Branches

JIRA-linked: <jira-key>/<descriptive-slug> (e.g. ag-12345/fix-tooltip-flicker)
No JIRA: <initials>/<descriptive-slug> (e.g. at/improve-watch-reload-time)
Release: b12.0.0 (see releases skill)
Slugs use kebab-case. JIRA key casing is flexible (both ag-12345 and AG-12345 are used).
Multiple tickets: join with underscore before the slug (e.g. CRT-1030_CRT-1044/fix-highlight)

Commits

First line: AG-XXXX <description> (uppercase JIRA key, imperative mood). A colon after the key is also acceptable: AG-XXXX: <description>.
No JIRA: <description> (imperative mood)
Keep the first line under 72 characters.
Multi-line: blank line after the first line, then body paragraphs or bullet points for additional context.
Never attribute agentic tooling (no "Co-authored-by", "Generated by", or similar).

相关技能

快速安装

Git Conventions

npx skills add ag-grid/ag-grid

下载 Skill 打开源码仓库

作者: ag-grid
星标: 15,227
更新时间: 2026年3月25日
职业

本页内容

Pull Requests

Base branch: Detect the base branch from git context — do not assume latest. If the current branch was created from a bX.Y.Z release branch, the PR must target that release branch. This includes any changes needed during the current release cycle — code fixes, skill/prompt updates, example fixes, doc corrections. Only target latest for work that doesn't need to ship with the current release. To determine the base, run .rulesync/skills/git-conventions/detect-base-branch.sh — it compares merge-base distances from HEAD to all origin/bX.Y.Z release branches (newest version first) and prints BASE_BRANCH=<branch>. Fall back to origin/latest if no release branch is closer. The user may not mention which base to use, so always detect it from git ancestry.
Title: AG-XXXX <description> for JIRA-linked; plain description otherwise. Under 70 characters.
Multiple tickets: comma-separate keys (e.g. CRT-1030, CRT-1044 Fix highlight)
Body (JIRA-linked): Always include: the JIRA ticket link, a Fix #AG-XXXX line (enables downstream automations), and a brief summary of what changed and why. The summary should be enough for a reviewer to understand the change without opening the ticket. Keep it concise — this is a public repo.
Body (no JIRA): concise description of what changed and why.
Never attribute agentic tooling.

Example JIRA-linked body:

Commits

03Pull Requests

软件开发人员

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Repository Setup

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

Significant-Gravitas183.5k

软件开发人员