plugins/sentry-skills/skills/create-branch/SKILL.md
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.
npx skillsauth add getsentry/skills create-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 prefix:
gh api user --jq .logingit config github.usergit config user.emailwhoamilocalResolve the work description:
$ARGUMENTS is present, use itgit diff
git diff --cached
git status --short
repo-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 <prefix>/<type>/<short-description>.
Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.
Choose the base without prompting:
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:]'
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:
git checkout -b <branch-name>
Report the final branch name, but do not stop for confirmation.
tools
Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.
development
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
documentation
Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket automatically from the issue's linear-linkback comment.
testing
Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.