Free · Private · No signup
Git Branch Name Generator
Make conventional branch names from a type, optional Jira ticket, and a short description. Copy git checkout -b in one click. Runs in your browser.
Branch details
Try an example, or fill the fields. Ticket is optional.
Feature, Fix, and Chore cover most work. The rest match Conventional Commits prefixes.
Jira, Linear, GitHub — whatever key your tracker uses.
Plain English is fine. We turn it into a hyphenated slug.
Live preview
Copy the checkout command, or just the branch name.
Branch name
feat/your-short-slug
Checkout
git checkout -b feat/your-short-slug
How it is built
- Type
- feat
- Ticket
- —
- Slug
- —
Add a description to generate the name.
Branch names your teammates can read
A git branch name generator saves you from inventing slugs under pressure. The same pattern — feat/PROJ-123/add-login — keeps history searchable and links work to the ticket. After you branch, schedule the deploy with the Cron Job Generator.
The branch name and git checkout -b … update as you type. Copy once — no generate button.
Drop in PROJ-123 (or any tracker ID) and it sits between the type and the slug.
Type “add login button”; get add-login-button. Hyphens, lowercase, no punctuation clutter.
100% client-side. Ticket keys stay on your machine.
How to use the git branch name generator
- 1
Pick a type
Start with Feature, Fix, or Chore. Use Docs, Test, or the others when that is what you are actually doing.
- 2
Add a ticket if you have one
Paste a Jira, Linear, or GitHub key. Skip this if the work is not tracked.
- 3
Describe the change
A short phrase is enough. The tool turns it into a hyphenated slug automatically.
- 4
Copy git checkout -b
Paste the command in your repo, or copy just the branch name if you create branches another way.
Frequently asked questions
What is a conventional git branch name?
A conventional branch name is type/optional-ticket/short-slug — for example feat/PROJ-123/add-login or fix/header-overflow. Anyone on the team can tell what the branch is for without opening the diff.
How do I include a Jira ticket in the branch name?
Put the key in Ticket number (PROJ-123, JIRA-88, ENG-4). The generator inserts it between the type and the slug: feat/PROJ-123/add-login. Linear, GitHub, and Asana IDs work the same way. Leave it blank if you do not use tickets.
Should I use feat or feature?
This tool uses feat, fix, and chore to match Conventional Commits (the same prefixes many teams use in commit messages). If your repo already uses feature/, keep that local convention — consistency in one repo matters more than the exact word.
What makes a good branch description?
Write a short phrase in plain English, starting with a verb when you can: add login button, not LoginButton_v2. Spaces become hyphens; punctuation is stripped. Keep it lowercase and specific enough that next month you still know what it was.
What does git checkout -b do?
It creates a new branch and switches you onto it in one step. Copy the command from this page and paste it in your repo folder. git switch -c does the same thing on newer Git versions.
Does this git branch name generator store my tickets?
No. Type, ticket, and description never leave your browser. There is no account and no upload.
Is the Git Branch Name Generator free?
Yes. No signup, no watermark, unlimited names and checkout commands.