Menu
Create a feature branch using this repo's branch-naming conventions.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
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 |
| description | Create a feature branch using this repo's branch-naming conventions. |
| allowed-tools | Bash, Read |
| argument-hint | <short-description> |
Create a feature branch that follows this repo's branch-naming conventions, then check it out.
Read the conventions. Read
docs/harness/vcs/branches.md for the naming rules this repo
follows. Respect every DONT listed there.
Derive the branch-name. Apply the rules in branches.md to the user's
description: lowercase, alphanumerics + hyphens only, collapse runs
of hyphens, trim leading/trailing hyphens. Keep it short (3–5 words).
Delegate to branch-vcs. Invoke the /branch-vcs <branch-name>:
Report. Print the branch name branch-vcs returned.
branch-vcs.