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.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
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 prefix:
First try gh api user --jq .login
Then git config github.user
Then the local part of git config user.email
Then whoami
Sanitize to lowercase ASCII letters, digits, and hyphens; if empty, use local
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 <prefix>/<type>/<short-description>.
Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.