Menu
Creates a vcs commit. Should rarely be called directly.
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
| name | commit-vcs |
| description | Creates a vcs commit. Should rarely be called directly. |
| allowed-tools | Bash |
| argument-hint | <message> [--files <f1> <f2> ...] |
Infra-layer wrapper around git add + git commit. Does not decide what
to commit or what to write — it just runs the shell call with consistent
flags.
Invoked by the commit capability skill once that skill has produced a
message and (optionally) a file list. You usually do not invoke this
directly — the capability layer is where judgment lives.
Delegate to the script:
.claude/skills/commit-vcs/scripts/commit.sh "<message>" [file1 file2 ...]
<message> — the full commit subject (+ optional body, newline-separated).file1 file2 ... — optional. When given, git add <files> runs first.
When omitted, the already-staged index is committed.The script refuses to run if the index is empty and no files were passed.
Co-Authored-By).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.
Create a commit following this repo's conventions (Conventional Commits). Use when the user asks to commit changes. Optional file list scopes the commit.
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.