菜单
Before making any non-trivial code, docs, or config change -- create a feature branch first, then open a PR. Never commit directly to main. Apply by default before any edit; this is the baseline branch discipline that all other git skills build on.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when deciding whether to dispatch a runner or a worker for a subtask. Describes the decision boundary, the failure mode when runner is used where worker is intended, and the safe composition pattern.
When a repo has no GitHub remote (or is not yet a git repo) -- use this to route survey, sweep, and dispatch off the GitHub-centric path. Detect with `git remote` empty; treat blank GitHub columns as expected, not an error; route work to commits + CLAUDE.md instead of issues + PRs; degrade a maintenance sweep to the local-only axes.
When the directive is "status check," "what's new across my projects," or "sweep maintenance" -- run a per-project, read-mostly, non-PR sweep. For each project under the owner-prefixed layout, gather stars/forks, open issues/PRs split into mine vs community vs bots, package downloads, release-due (unreleased conventional commits), a test run, a stale-CLAUDE.md flag, and branch-cleanup candidates. Emit a fresh per-project report every sweep; NEVER cache status back into a workspace/manager CLAUDE.md.
When the issue or PR queue has open unlabeled items -- run a read-only triage pass that labels each one by component, category, priority, and size, flags duplicates, closes noise, and reports the p1 queue before runners are dispatched.
When writing any issue, PR, or commit message, use this for the authoring standard. Covers structure (headings, lists, tables, fenced blocks, the bug block, the before/after) and voice (factual, no emdashes, no editorializing labels, conventional-commit prefixes, no commit trailers).
The canonical owner-prefixed workspace layout. Every repo lives at ~/Code/<host>/<owner>/<repo> -- no active/ or language segment. Enumerate with `ls ~/Code/github.com/*/*`; resolve siblings by path arithmetic. The manager (workspace-root) CLAUDE.md is a map of where things are and how to read them, never a cache of per-project inventory or status. Load this whenever a session reasons about where a repo lives, walks the workspace, or resolves one project from another.
| name | git-branch-pr-workflow |
| description | Before making any non-trivial code, docs, or config change -- create a feature branch first, then open a PR. Never commit directly to main. Apply by default before any edit; this is the baseline branch discipline that all other git skills build on. |
| allowed-tools | Bash(git *) Bash(gh *) |
Default to git checkout -b <type>/<description> before any
edits. Never commit directly to main, even on solo projects.
Conventional commit prefixes: feat, fix, refactor, chore,
ci, docs, test. Push branch, open PR, let the user (or the
dispatcher loop) merge.
git checkout -b <type>/<short-description>.<type>: <description>; ! marks breaking).git push -u origin <branch>.gh pr create [--draft] with a tight body that
references the underlying issue (use a Closes #N keyword in the
PR body so the merge closes the linked issue).gh pr merge --squash --delete-branch.feat: ... -- new user-visible behaviorfix: ... -- bug fixrefactor: ... -- internal restructuring, no behavior changechore: ... -- repo maintenance (dependencies, config, etc.)ci: ... -- CI/release-process changesdocs: ... -- documentation onlytest: ... -- tests onlyAppend ! to mark a breaking change: refactor!: cut --head and --tail (closes #42).
The same prefixes apply to issue titles, not only commits,
branches, and PR titles. An issue that proposes a new skill is
feat: ...; an issue documenting a bug is fix: .... The
triage skill normalizes issue titles to this scheme.
Do not include "Generated with Claude Code" or "Co-Authored-By"
trailers on any commit. The commit author is always the repo
owner (Josh Rotenberg <joshrotenberg@gmail.com>); no
co-author is added. After committing, verify before pushing:
git log -1 --format='%an <%ae>%n%(trailers)'
The author line must be the repo owner and the trailers must be
empty. If a trailer slipped in, amend it out (git commit --amend)
before pushing.
git-fix-pr-branching -- how
to handle fixes when a PR is open vs merged.heredoc-backticks -- formatting
the PR body without breaking the markdown.