Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
Start a fresh conversation. Replace the highlighted placeholders.
Use create-branch to Create a Sentry-style git branch for [work description], choosing its base and a collision-free name according to the documented workflow, then report the branch name.
Required inputs
[work description]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: create-branchdescription: Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.argument-hint: '[optional description of the work]'
Create Branch
Create a git branch following Sentry naming conventions.
Keep this workflow non-interactive unless the user explicitly asks to choose the name manually.
Workflow
Resolve the work description:
If $ARGUMENTS is present, use it
Otherwise inspect:
git diff
git diff --cached
git status --short
If there are local changes, derive a short description from the diff
If there are no local changes, use a generic description like repo-maintenance, tooling-update, or work-in-progress
Classify 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.