Help us improve
Share bugs, ideas, or general feedback.
From sentry-skills
Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.
npx claudepluginhub getsentry/skills --plugin sentry-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/sentry-skills:create-branch [optional description of the work][optional description of the work]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a git branch following Sentry naming conventions.
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.
Creates and switches to a new Git branch from an inline description, conversation context, or local diffs. Preserves uncommitted changes. Use for starting fresh or moving in-progress work to a named branch.
Share bugs, ideas, or general feedback.
Create a git branch following Sentry naming conventions. Keep this workflow non-interactive unless the user explicitly asks to choose the name manually.
Resolve the work description:
$ARGUMENTS is present, use itgit diff
git diff --cached
git status --short
repo-maintenance, tooling-update, or work-in-progressClassify the branch type:
| Type | Use when |
|---|---|
feat | New functionality |
fix | Broken behavior now works |
ref | Behavior stays the same, structure changes |
chore | Maintenance of existing tooling/config |
perf | Same behavior, faster |
style | Visual or formatting only |
docs | Documentation only |
test | Tests only |
ci | CI/CD config |
build | Build system |
meta | Repo metadata |
license | License changes |
When unsure: use feat for new things, ref for restructuring, chore for maintenance.
Generate <type>/<short-description>.
Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.
Choose the base without prompting:
git branch --show-current
git remote | grep -qx origin && echo origin || git remote | head -1
git symbolic-ref refs/remotes/<remote>/HEAD 2>/dev/null | sed 's|refs/remotes/<remote>/||' | tr -d '[:space:]'
main, then master, then the current branchAvoid collisions by appending -2, -3, and so on until the name is unused locally and remotely.
Create the branch:
git checkout -b <branch-name>
Report the final branch name, but do not stop for confirmation.