Setting the chapter. One moment.
Skills
Chapter 8 of 28
Create a git branch following Sentry naming conventions.
1 minute · 214 words · 2 sections
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 itgit diff
git diff --cached
git status --short28 chapters · 88 min
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 <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.
Install this repository
npx skills add getsentry/skills/plugin marketplace add getsentry/skillsSkills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.
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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
main, last pushed 8 August 2026.SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Sentry, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./getsentry/skills.md, and each chapter at its own .md URL.