What it does
Branch Namer turns messy task descriptions into clean, kebab-case branch names that follow a consistent pattern: type/scope/description — for example feat/auth/add-oauth-google or fix/payments/stripe-webhook-timeout. It detects the work type from context (feature, fix, chore, hotfix, release) and strips filler words that add noise without meaning.
When you paste a Jira or Linear ticket URL or ID, the skill generates the branch name with the ticket ID prefix — e.g. PROJ-1234/feat/payment-retry-logic. This keeps branches traceable back to tickets without any manual copy-pasting. It also enforces a configurable maximum length so branches stay readable in tight terminal widths.
How to install
npx skills add user/branch-namerHow to use
Describe the work you're about to do and ask Claude to name the branch:
Name a branch for: Add Google OAuth login to the authentication module
Output:
feat/auth/add-google-oauth git checkout -b feat/auth/add-google-oauth
Configuration
# Include a Linear ticket ID Name a branch for Linear ticket ENG-421: fix checkout crash on Safari # Use GitLab merge request style Use GitLab style branch names for: refactor API middleware # Enforce max length Name a branch, max 40 characters: implement user preference settings panel
Tip: Add Branch Namer to your team's CLAUDE.md so every contributor generates branch names using the same convention automatically — no style guide needed.
Related skills
Pair Branch Namer with Smart Git Commit to automate the full commit lifecycle — consistent branch names and consistent commit messages in every workflow.