Stats
Actions
Tags
From git
Create a new git branch with a well-named branch following the convention. Use this skill whenever the user wants to create a new branch, switch to a new branch, or start working on a new feature/fix/task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git:branch-namingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new git branch following the `<type>/<short-description>` naming convention.
Create a new git branch following the <type>/<short-description> naming convention.
<type>/<short-description>
| Type | When to use |
|---|---|
feat | New feature or functionality |
fix | Bug fix |
docs | Documentation only |
style | Formatting, whitespace, no code change |
refactor | Code restructuring without behavior change |
test | Adding or updating tests |
chore | Build, CI, dependencies, tooling |
feat/add-user-authfix/null-pointer-crashdocs/update-readmerefactor/extract-parserchore/bump-dependenciestest/add-api-testsgit branch --show-currentgit checkout -b <type>/<short-description>npx claudepluginhub t0k0sh1/agent-plugins --plugin gitCreates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.
Creates git branches following Sentry naming conventions. Automatically determines branch type and description from arguments or local diff. Useful when starting new work.
Creates Git feature branches with short auto-incremented names and type prefixes (feat/fix/refactor/chore/docs). Generates from manual descriptions, uncommitted changes, or Arkhe SDLC specs.