Menu
Create a commit following this repo's conventions (Conventional Commits). Use when the user asks to commit changes. Optional file list scopes the commit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a feature branch using this repo's branch-naming conventions.
Creates a new vcs branch. Should rarely be called directly.
Decompose the working tree into clean commits and open a PR. Use when the user asks to ship the current change end-to-end.
Creates a vcs commit. Should rarely be called directly.
Opens a vcs pull request. Should rarely be called directly.
Partition the current working tree into the smallest coherent commit chunks. Use when a diff spans multiple concerns and needs to be split.
| name | commit |
| description | Create a commit following this repo's conventions (Conventional Commits). Use when the user asks to commit changes. Optional file list scopes the commit. |
| allowed-tools | Bash, Read |
| argument-hint | [files...] |
Create a single git commit that follows this repo's commit conventions.
Scope the change.
commit-vcs).Read the conventions. Read
docs/harness/vcs/commits.md for the Conventional-Commits rules this
repo follows. Respect every DONT listed there (notably: no
Co-Authored-By: Claude).
Understand the diff. Run git status and git diff --cached
(or git diff -- <files> if a file list was passed and nothing is
staged yet). Read the actual changes — do not rely on file names alone.
Draft the message.
<type> (feat / fix / refactor / docs / test / chore).<scope> when the change is localised to one area (e.g. api,
web, docs).Delegate to commit-vcs. Invoke the infra wrapper with the message
and (if applicable) the file list:
.claude/skills/commit-vcs/scripts/commit.sh "<message>" [<files>]
Report. Print the commit hash commit-vcs returned, plus the
subject line.
/identify-commits instead.