getsentry/skills · Official

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.

All-time #3716 Trending #6940 First seen Mar 4, 2026
8-week activity · all time api

Installation

$ npx skills add getsentry/skills --skill create-branch

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from getsentry/skills · top by installs.

npx skills add getsentry/skills

Browse all from getsentry/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 986
License LICENSE
Default branch main
Open issues 5
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,528 B
  • docs SUMMARY.md 238 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,800 installs

SKILL.md

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

  1. Resolve the work description:

- If $ARGUMENTS is present, use it - Otherwise inspect: ``bash 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`

  1. 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.

  1. Generate <type>/<short-description>.

Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.

  1. Choose the base without prompting:

``bash 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:]' ` - If default branch detection fails, fall back to main, then master`, then the current branch - If on a detached HEAD, branch from the current commit - If already on a non-default branch, branch from the current branch - Only switch to the default branch when the user explicitly asks

  1. Avoid collisions by appending -2, -3, and so on until the name is unused locally and remotely.
  1. Create the branch:

``bash git checkout -b <branch-name> `` Report the final branch name, but do not stop for confirmation.

References