npx skills add ...
npx skills add getsentry/skills --skill create-branch
npx skills add getsentry/skills --skill create-branch
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.
The same skill content is published under more than one repo. The install counts are split across them; any of these commands works.
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 itrepo-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:
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:
Report the final branch name, but do not stop for confirmation.