Create Convention-Compliant Git Branches Automatically

Create Branch generates a git branch name in the <username>/<type>/<short-description> format used by Sentry's branch-naming convention, then creates it safely. It gets the username prefix from gh api user --jq .login, or asks if that fails, determines the work description from $ARGUMENTS, an uncommitted diff, or by asking the user, and classifies the type against a twelve-value table - feat, fix, ref, chore, perf, style, docs, test, ci, build, meta, license - defaulting to feat for new things, ref for restructuring, and chore only for maintaining something that already exists. It builds a kebab-case, 3-6-word short description using only ASCII letters, digits, and hyphens, presents the proposed name for confirmation or editing, then handles branch creation carefully: detecting the current and default branch, falling back from symbolic-ref to checking for main/master if needed, warning if you're not on the default branch and offering to switch (stashing and later restoring any uncommitted changes), checking the proposed name doesn't already exist locally or on the remote via git show-ref, and only then running git checkout -b <branch-name>.

Use it when starting new work and you need a branch name that follows the repository's naming convention, need help classifying the work as feat, fix, docs, or another type, or want a name proposed from either a task description or the current local diff. It's specifically Sentry's convention, <username>/<type>/<description>, so it's not the fit for a repo with a different branch-naming standard without adapting the type table and prefix rules.

Input: a work description, either passed directly, inferred from git diff/git status, or asked for, plus the GitHub username from gh api user. Output: a confirmed branch name and, once approved, a newly checked-out git branch off the correct base, with any pre-existing uncommitted changes preserved through a stash-and-restore if a branch switch was needed first.

• GitHub CLI (gh api user) for the username prefix
• Git (diff, status, branch, symbolic-ref, show-ref, checkout -b, stash) for detecting state and creating the branch
• Sentry's branch-naming standard as the reference convention

Example outputs the skill's own reference gives include priscila/fix/dropdown-not-closing-on-blur and priscila/feat/add-search-to-conversations.

Anyone starting new work in a Sentry-convention repository who wants a correctly typed, named, and safely created branch without manually working out the prefix, type, and base-branch logic each time.