Git Branch Name Generator
Generate standardized branch names following best practices
About this ToolHow it works, benefits & use casesTap to collapse
Compose a clean, conventional Git branch name from a few inputs instead of inventing one by hand. Pick a branch type — feature, bugfix, hotfix, release, chore, refactor, docs, or test — type a short description, and the generator slugifies it into the case style you choose (kebab, snake, or camel), joining the parts with your preferred separator (/, -, or _). Add an optional ticket number for traceability and optionally prefix your username. The branch name updates live as you type, and it is validated against real Git rules: it rejects spaces and characters like ~ ^ : ? * [ ] \, leading or trailing slashes, consecutive slashes, names ending in .lock, the @{ sequence, and names over 255 characters. You also get alternative suggestions (different separators, a version without the ticket, a short type-and-description variant) plus worked examples. The result lives in a shareable URL and copies in one click.
How to Use
- 1Choose a Branch type from the dropdown — its description explains what the type is for.
- 2Enter a short Description of the work; the generated name updates live as you type.
- 3Optionally add a Ticket number for traceability and pick a Separator (/, -, or _).
- 4Choose a Case style — kebab, snake, or camel — and optionally enable "Include username" with your handle.
- 5Copy the generated branch name, pick one of the Alternative suggestions, or share the URL.
Key Benefits
- Eight conventional branch types from feature to hotfix to docs
- Slugifies your description into kebab, snake, or camel case
- Choice of /, -, or _ separators to match team convention
- Optional ticket number and username prefix for traceability
- Live validation against Git's real branch-name rules
- Alternative suggestions, including separator and ticket-free variants
- Live updates plus a shareable URL and worked examples
Common Use Cases
- Naming a feature branch consistently with a JIRA or GitHub issue number
- Enforcing a team-wide branch convention without a custom script
- Generating a hotfix branch name quickly during an incident
- Standardizing separators and casing across contributors
- Sharing a proposed branch name with a teammate via a single link
Branch configuration
New feature or enhancement
Brief description of the branch purpose
Issue or ticket number
Updates live as you type
Fill in a description to generate a branch name.
Examples
Type: feature | Description: user authentication | Ticket: JIRA-123
feature/JIRA-123/user-authenticationType: bugfix | Description: fix login error | Ticket: BUG-456
bugfix/BUG-456/fix-login-errorType: hotfix | Description: critical security patch
hotfix/critical-security-patchType: refactor | Description: improve database queries
refactor/improve-database-queriesBranch naming best practices
- Use descriptive names that explain the purpose of the branch.
- Include ticket/issue numbers for traceability.
- Use consistent separators across your team.
- Keep branch names concise but meaningful.
- Prefix with type (
feature/,bugfix/,hotfix/) for clarity. - Avoid special characters that might cause issues in Git.
- Delete merged branches to keep the repository clean.
Was this tool helpful?
Share Your Experience
Help others discover this tool!
Related tools
- Component Name GeneratorTurn a description into ranked, kind-aware component names with a file scaffold and a name validator (casing, collisions, clarity)
- Heroku Procfile GeneratorBuild a Heroku Procfile and matching app.json — process types, env vars, addons, dyno formation — plus a Procfile parser and audit
- Markdown TOC GeneratorGenerate table of contents for Markdown
- Package.json Scripts GeneratorGenerate common npm scripts for different project types and workflows
- Tailwind Config GeneratorVisually build a Tailwind config - theme extend, colors, spacing, fonts, screens, plugins - and export it as a v3 JS config or a v4 @theme CSS block
- App Icon GeneratorTurn one image into complete icon sets for iOS, Android, Web/PWA & macOS — Contents.json, adaptive icons, maskable, manifest & favicon.ico — in one ZIP
You can choose feature (new work), bugfix, hotfix (critical production fix), release, chore (maintenance), refactor, docs, and test. The selected type becomes the first segment of the branch name and its description is shown beneath the dropdown.
The description is lowercased, stripped of special characters, and spaces are collapsed into your separator. The case style then shapes it: kebab keeps dashes (my-branch), snake converts to underscores (my_branch), and camel removes separators and capitalizes the next letter (myBranch).