菜单
Stage and commit using this repo's commit message convention
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the project issue tracker. Use when the user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Capture rough notes locally with zero ceremony, then export them to their right permanent home. Use when the user wants to jot/park/stash a thought mid-task without derailing ("note to self", "remember to", "journal this"), or when they later want to export/file/route parked notes into an issue, spec, ADR, CONTEXT term, or docs. Capture is local and gitignored; export delegates to whichever existing skill owns the note's permanent home.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Implement a piece of work based on a spec or set of tickets.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | commit |
| description | Stage and commit using this repo's commit message convention |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*) |
| user-invocable | true |
Current branch:
!git branch --show-current
Git status:
!git status
Staged + unstaged diff:
!git diff HEAD
Recent commits:
!git log --oneline -5
Extract the ticket number from the current branch name using pattern: {number}-{description} — the leading number is the GitHub issue (e.g., branch 533-csv-upload-download-rules → ticket #533)
Review the diff and stage all relevant changed files (avoid staging unrelated or generated files)
Write a commit message in the format: #{ticket_number} - {concise description of changes} — example: #501 - fmt
Keep the {concise description} caveman-terse (borrowed from the caveman skill): imperative, drop articles and filler, fragments fine, abbreviate common terms (fmt, refactor, deps, config), aim for 2-8 words. Prefer #533 - add CSV upload endpoint over #533 - this commit adds a new endpoint for uploading CSV files.
Commit in a single operation using a HEREDOC for the message:
git commit -m "$(cat <<'EOF'
#NNN - description here
EOF
)"
Run git status to confirm the commit succeeded