with one click
branch-vcs
Creates a new vcs branch. 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.
Menu
Creates a new vcs branch. 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
Create a feature branch using this repo's branch-naming conventions.
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.
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 | branch-vcs |
| description | Creates a new vcs branch. Should rarely be called directly. |
| allowed-tools | Bash |
| argument-hint | <branch-name> |
Infra-layer wrapper around git checkout -b. Does not decide what to
name the branch — it just runs the shell call with the name it's given.
Invoked by the branch capability skill once that skill has assembled
the full branch name from the type prefix and slug. You usually do not
invoke this directly — the capability layer is where judgment lives.
Delegate to the script:
.claude/skills/branch-vcs/scripts/checkout.sh "<branch-name>"
<branch-name> — the fully assembled <type>/<slug> (e.g. feat/add-date-filtering).git checkout -b "$name".