Why it matters
Teams agree a branch convention, then type it slightly differently every time. Consistent names make CI rules and ticket links work.
The name is checked against git's ref-name rules so it never fails on odd punctuation.
How to use it
- Type or paste your input; the example shows the format.
- Press Make branch name. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
Which characters can't go in a branch name?
Spaces, ~ ^ : ? * [ and backslash, '..', '@{', a trailing dot or '.lock'.
Should the ticket ID come first?
Usually yes, after the type, so tools like Jira and Linear link the branch automatically.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.