Labsco
getsentry logo

create-branch

✓ Official★ 844

by sentry · part of getsentry/skills

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…

🔥🔥✓ VerifiedFreeQuick setup
#automation#devops#git#monitoring
🧩 One of 7 skills in the getsentry/skills package — works on its own, and pairs well with its siblings.

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…

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by sentry

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… npx skills add https://github.com/getsentry/sentry-skills --skill create-branch Download ZIPGitHub844

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:

Copy & paste — that's it
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.

Choose the base without prompting:

Copy & paste — that's it
git branch --show-current
git remote | grep -qx origin && echo origin || git remote | head -1
git symbolic-ref refs/remotes/ /HEAD 2>/dev/null | sed 's|refs/remotes/ /||' | 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

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

Create the branch:

Copy & paste — that's it
git checkout -b

Report the final branch name, but do not stop for confirmation.

References