type, scope, ticket, separator, and casing — then generate names instantly or validate a pasted list of branches against the same rules. Includes a copy-paste git guard so the convention is enforced on push.Git Branch Naming Generator
Build branch names from a convention you define, generate them in bulk, and validate existing branches against the same rules.
All processing happens locally in your browser — branch names never leave the page.
type — the intent of the change, from a fixed list.
scope — optional area, like api, ui, or auth.
ticket — optional id linking the branch to a tracker.
description — short, imperative, normalized into the chosen casing.
Separator joins type/scope/ticket; casing applies to the description.
The Validate tab runs the same pattern against pasted branch names and flags offenders with reasons.
It also emits a copy-paste pre-push guard so the same checks run on your machine before any push.
0
branches
0
max length
About Git Branch Naming Generator
Define your branch convention once —
Features
Configurable type, scope, ticket, and description segments,Separator choice: slash, dash, dot, or underscore with casing control,One-click generation plus bulk generation from a ticket list,Validator with per-branch pass/fail and a summary report,Reserved-name and length limits with a copyable git guard
How to Use
1. Pick a type and, optionally, a scope and a ticket prefix. 2. Type a short description (spaces are normalized). 3. Generate and copy the branch name. To validate, switch to the validate tab and paste branch names one per line.
Examples
feature/JIRA-1234/add-billing-report — a feature with ticket and scope-less kebab description. hotfix/ops-7/fix-logout-crash — a hotfix referencing an ops ticket. The validator flags branches like feature/Add Billing or master with the reason.
Benefits
Teams stop guessing names, tickets map straight to branches, and the same convention is enforced locally before a push. No server, no setup, works offline.
Frequently Asked Questions
Is my branch data sent anywhere?
No. Everything, including pasted branch lists, is processed locally in your browser. No network requests are made and nothing is stored server-side.
What conventions does the generator support?
Any combination of type (feature, bugfix, hotfix, chore, release, docs, test, perf, refactor), optional scope, optional ticket id, and a free-form description, separated by slashes or dashes with a chosen casing (kebab, snake, camel, Pascal, or UPPER).
How does the validator work?
Paste one branch name per line and it checks each against the active pattern: type whitelist, optional scope/ticket, allowed characters, length limit, and forbids reserved names such as main, master, or develop.
Why are main, master, and develop rejected?
Those are shared integration branches, not working branches. The validator treats them as reserved unless you explicitly allow them, so feature work cannot accidentally target protected branch names.
Does it integrate with a git hook?
The tool offers a ready-to-paste commit-msg/pre-push style bash guard that runs the same rule locally, so convention is enforced at push time, not just by a code review.
Can I generate branches in bulk?
Yes. With a ticket prefix enabled you can paste multiple ticket ids (one per line) and the generator emits one branch name per ticket with a shared description.
What is the recommended convention?
A widely used default is <type>/<ticket>-<kebab-description>, e.g. feature/JIRA-1234-add-billing-report. The tool defaults to that but every part is configurable.
Are multi-word descriptions handled?
Yes. Spaces and underscores are normalized to the separator you choose, so "Add billing report" becomes add-billing-report (kebab) or AddBillingReport (camel), depending on your casing setting.