Build a message to the Conventional Commits specification with the correct footer forms, validated as you type, showing which version bump it implies.
Valid — implies a minor release
One of the two types the specification itself defines.
50 characters in the header. 72 is the usual limit.
Imperative mood, lower case, no full stop — “add” rather than “added”.
Why, not what. The diff already says what changed.
Issue numbers, comma separated. The # is added for you.
One per line, as Name <email>. GitHub only reads these from the last paragraph.
feat: add a colour contrast checker to the toolbarfeat implies a minor release. That only takes effect if your release tooling reads conventional commits — the convention is a format, not a mechanism.
Conventional Commit Generator runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Conventional Commits is a format with a purpose: a message that follows it can be read by tooling to work out the next version and write the changelog. That only works if the format is exact, and the parts that have to be exact are the parts least likely to be remembered.
The version impact is shown as you type because it is the whole point of the convention. `feat` is a minor bump, `fix` is a patch, and a `!` or a BREAKING CHANGE footer makes it a major — whatever the type is. A `fix!` is a major release, which is the rule most people have backwards.
The footer forms are the fiddly bit. `BREAKING CHANGE` is spelled with a space, not a hyphen, and is the one footer token in the specification written that way. A `Co-authored-by:` trailer only counts if it is in the last paragraph with no blank line inside it — GitHub ignores it otherwise, and nothing tells you it was ignored.
Everything the generator produces is run back through the same validator the checker tool uses. A generator that can emit something its own validator rejects is a generator nobody should trust, so the two are wired to agree.
The description is the only part the specification actually requires. Everything else here is optional, and a short good message beats a long ceremonial one.
No. It is `BREAKING CHANGE` with a space — the one footer token the specification spells that way, because every other footer uses a hyphen in place of spaces. `BREAKING-CHANGE` is accepted as a synonym by the specification, but the space form is the one tooling expects.
Yes. A breaking change is a major bump whatever type carries it. The type describes the kind of change; the ! describes its compatibility impact, and the second decides the version.
The specification is silent, and in practice tools disagree. Most treat a breaking change below 1.0.0 as a minor bump rather than taking you to 2.0.0. If that matters, pin the behaviour in your release tool's configuration rather than relying on the default.
Almost always because it is not in the last paragraph. GitHub only reads trailers from the final block of the message, with no blank line inside it. A trailer after a blank line in the middle of the body is ignored silently.
Only if something reads it. The convention is a format, not a mechanism — it does nothing until a release tool, a changelog generator or a commit linter is configured to use it.