Branch Name Generator

Why branch names matter more than you think

A branch name is a tiny label, but it is read dozens of times: in git branch listings, in pull request titles, in CI logs, in your teammates' terminals. A consistent naming scheme makes all of that legible at a glance. An inconsistent one - mix of camelCase, random spaces, capital letters, someone's name - turns your branch list into noise. This generator takes a type, a ticket, and a short description and produces a clean, lowercase, kebab-case branch name that reads the same across your whole team.

It runs entirely in your browser. Type your inputs and the name updates live; nothing is sent anywhere.

The convention this tool follows

The generated pattern is type/TICKET-short-description, for example feat/PROJ-12-add-login-page. This mirrors the Conventional Commits type prefixes, so your branches speak the same language as your commit history. The type says what kind of work it is, the ticket links it back to your tracker, and the description makes it human-readable. Everything after the type is normalized to kebab-case: lowercase letters, numbers, and hyphens only.

The rules being applied

• Lowercase everything except the ticket ID, which is uppercased (PROJ-12) since trackers use uppercase keys.
• Replace spaces and punctuation with single hyphens - no double hyphens, no leading or trailing hyphens.
• Keep only characters that are safe on every git host: letters, numbers, hyphens, and the single type slash.
• Trim the description, never the ticket, when the name would exceed your max length - the ticket link is the part you cannot afford to lose.
• Avoid slashes inside the description so the name stays a clean two-part path.

Keep names short and specific

A good branch name is specific enough to know what it does but short enough to type and read. feat/PROJ-12-add-login-page is great. feat/PROJ-12-add-the-new-login-page-with-oauth-and-remember-me-and-error-states is not - it is a commit message pretending to be a branch name. The max-length slider above enforces a ceiling and trims the description to fit, so you get a name that stays under control. Aim for roughly 30 to 50 characters.

Using branch names with Claude Code

When you run Claude Code with git worktrees for parallel agents, branch names double as folder names and session labels. A clean convention pays off immediately: feat/PROJ-12-add-login and fix/PROJ-14-token-refresh tell you at a glance which agent is doing what. Feed the generated name straight into git switch -c, or hand it to Claude Code and ask it to create the branch and start working. Consistent names keep your worktree list readable even with five agents running.

Fitting your team's variant

Some teams use username/feature, some use feature/ticket, some drop the ticket entirely. The type/ticket-description pattern here is a solid default that works for most teams and matches Conventional Commits, but the important thing is that everyone uses the same one. Pick a convention, write it in your CONTRIBUTING or CLAUDE.md file, and generate every branch the same way. Consistency is worth more than any particular format.