Git Branch Name Generator

What this generator does

Joins a type prefix (feature, fix, chore, hotfix and similar) to a kebab-case description with a slash, the convention most Git workflows use to sort branches by intent at a glance. The prefix is not decoration: a CI pipeline or a branch-protection rule can trigger on it, so feature/ and hotfix/ often take genuinely different paths through review.

What it builds, and how many ways

Each result is assembled to this shape: [type] + [slug].

• slug: 30 options
• type: 12 options

Taken together those banks can be assembled 360 different ways, repeating after about 24.

Some results it can produce:

• feature/add-csv-export
• refactor/debounce-search-input
• revert/log-failure-reason
• hotfix/cart-total-rounding

A fixed sample so this page stays the same between visits. Your own results are assembled at random, each slot filled independently and each press independent of the last, so the same result can come up twice — past the repeat figure above, seeing one twice is more likely than not.

How to use this tool

1. Press generate for a branch name.
2. Generate again for another one.

Common use cases

• Teaching Git branch-naming conventions
• Placeholder examples in documentation
• Quick naming-convention inspiration

Limitations and good to know

• The type and the description are drawn independently from fixed word banks, 360 combinations in total, each shown once before any repeat — so a docs/ or revert/ branch can name a code change it would never hold.
• The description names a generic action, not your actual change — it is a format example, and the ticket or feature it should describe is yours to substitute in.

Practical tips

• Keep the ticket reference in the branch name — future you will want to find the branch from the issue, not the other way round.
• Agree a prefix convention across the team; mixed conventions make branch lists much harder to scan.