Create Convention-Compliant Git Branches Automatically

Create Branch creates a git branch with the correct type prefix and a descriptive name, following Sentry naming conventions. The branch name has the form of a username, a type and a short description separated by slashes. It proposes the name from either the task description or the current local diff, and asks you to confirm before creating anything.

The workflow has five steps:

• Get the username prefix by running gh api user --jq .login to read the GitHub username. If the command fails, for example when not authenticated, it asks you for your preferred prefix.
• Determine the description. If an argument is provided it is used as the description of the work. Otherwise it checks local changes with git diff, git diff --cached and git status --short. If changes exist it reads the diff to understand the work and generates a description, and if there are none it asks what you are about to work on.
• Classify the type from a table: feat for new user-facing functionality, fix for broken behavior that now works, ref for the same behavior with a different structure, chore for dependencies, config, version bumps or updating existing tooling without new logic, perf for the same behavior but faster, style for CSS, formatting or visual-only changes, docs, test, ci, build, meta for repo metadata, and license. When unsure, use feat for new things including new scripts, skills or tools, ref for restructuring existing things, and chore only when maintaining something that already exists.
• Generate and propose the name. The short description must be kebab-case and lowercase, 3 to 6 words, concise but clear, describe the change and not file names, and use only ASCII letters, digits and hyphens, with no spaces, dots, colons, tildes or other git-forbidden characters. It presents the name and asks if you want to use it, modify it or change the type. Examples include a fix for a dropdown not closing on blur, a feature adding search to a conversations page, a refactor simplifying drawer components and a chore bumping a dependency.
• Create the branch once confirmed. It detects the current branch and the default branch, using the remote HEAD reference and falling back to checking whether main or master exists, and asking if both or neither exist. If HEAD is detached, it shows the current commit and asks whether to branch from it or switch to the default branch first. If the current branch is not the default, it warns and asks whether to branch from the current branch or switch. When switching, it offers to stash uncommitted changes, and on any failure it restores stashed changes and stops. Before creating the branch it checks that the name does not already exist locally or on the remote, and if it does it asks for a different name. Then it runs git checkout -b with the name and restores any stashed changes.

Use it when you need a new git branch that follows the repository's naming convention, when you are starting new work from the default branch and need help classifying it, or when you want the name proposed from the task or the local diff. Trigger phrases include "create a branch", "new branch", "start a branch" and "switch to a new branch". It is scoped to Sentry naming conventions. It does not replace environment-specific validation or expert review, and it stops to ask for clarification if inputs, permissions or safety boundaries are unclear.

The input is an optional description of the work, or the local diff. The output is a proposed branch name for confirmation and, once confirmed, a newly created and checked-out branch.

gh api user --jq .login

It uses the GitHub CLI (gh) and git, and follows the Sentry SDK branch naming standard.

Developers on Sentry-style repositories, and teams that want consistent, typed branch names without thinking about the convention each time.