Pull Request Title Generator
Generates a conventional-commit-style pull request title — type plus a short description — as a naming-convention reference or placeholder for a demo repository.
What this generator does
Produces a pull request title in conventional-commit form — a type prefix and an imperative summary, joined by a colon. The value is the shape rather than the words: a title in this form is machine-readable, which is what lets changelogs and version bumps be derived from history instead of written by hand.
What it builds, and how many ways
Each result is assembled to this shape: [type] + [description].
- description: 30 options
- type: 11 options
Taken together those banks can be assembled 330 different ways, repeating after about 23.
Some results it can produce:
- fix: extract shared validation logic into a helper
- test: stop logging the full request body on validation failure
- revert: stop the migration running twice on a cold start
- docs: add retry logic to the payment webhook
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
- Press generate for a PR title.
- Generate again for another one.
Common use cases
- Naming-convention reference
- Demo repository placeholder data
- Onboarding new contributors to a convention
Limitations and good to know
- No scope segment is generated — the output is always type: description, without the optional (scope) some conventional-commit setups add between them.
- Type and description are drawn independently from fixed lists, so the pairing (a fix: title next to a description that reads like a new feature, say) may not make coherent sense together.
- It's a title only; the actual PR description, linked issues and diff are entirely up to you.
Practical tips
- Write the summary as a command — "add", not "added" or "adds". Every conventional-commit tool assumes the imperative, and mixed tense is what makes generated changelogs read badly.
Each part of the result is chosen independently with your browser's cryptographic random number generator, so every option in a bank is equally likely. How Generate Random works.
Frequently asked questions
- Does this include the optional scope some teams add, like feat(auth):?
- No — this generator produces the type and description only, joined by a colon, without a scope segment. If your team's convention includes one, you'd add it by hand after generating.
- Why does conventional-commit format matter?
- Because it's machine-parseable — tooling can scan commit and PR history for fix:, feat: and breaking-change markers to generate a changelog and decide the next semantic version automatically, rather than someone writing both by hand after the fact.