| name | branch |
| description | Create git branches named by conventional-commit type: <type>/<kebab-description>. Use when: creating any new git branch, starting work that needs a branch, or naming a branch. Triggers on: 'create branch', 'new branch', 'branch off', 'checkout -b', '/branch'. |
| allowed-tools | Bash |
| argument-hint | [work description or ticket] |
Conventional Branch Names
Branch names use the same type vocabulary as conventional commits:
<type>/<short-kebab-description>
Examples: feat/user-auth, fix/login-crash, refactor/api-client, chore/update-deps.
Rules
- Type — the conventional-commit type the dominant commit on this branch would have:
feat, fix, refactor, perf, docs, test, build, ci, chore, revert.
- Description — 2–4 words, kebab-case, specific: what the branch delivers, not how. Lowercase only, no spaces.
- Ticket IDs — if the work has a ticket, put its ID after the type:
feat/lin-123-user-auth.
- No agent-branded prefixes — never
codex/..., claude/..., or agent/.... The branch describes the work, not the tool that wrote it.
- Base — branch off the up-to-date default branch unless the work explicitly builds on the current branch.
Procedure
- Derive type and description from the requested work (or "$ARGUMENTS" if provided).
- Validate:
git check-ref-format --branch <name>.
- Create:
git switch -c <name>.
