Developer / Git

Conventional Commit Message Helper (Generator and Checker)

Build a commit message in the Conventional Commits 1.0.0 format: pick the type, add a scope and description, mark breaking changes, add a body and footers, and see the release a tool like semantic-release would make from it.

Conventional Commit Message Helper (Generator and Checker): The tool writes the first line as type(scope): description, with ! after the scope for a breaking change, then the body and footers after blank lines, including BREAKING CHANGE: with your migration note. It warns about a first line longer than 72 characters, a full stop at the end, and a capital first letter, and shows whether the commit would trigger a major, minor, or patch release. Runs 100% locally in your browser with zero server file uploads.

Category
Developer tools
Runs
In your browser
Cost
Free · no sign-up
Availability
Ready to use
Commit message helperLocal processing

Runs entirely in your browser

Commit message

feat(auth): add login with passkeys

35 characters in the first line · release: minor (new feature)

Conventional Commits 1.0.0: type(scope): description, an optional body after a blank line, and footers such as BREAKING CHANGE:. A ! after the type marks a breaking change. Tools such as semantic-release and release-please read these messages to pick the next version number and write the changelog.

Example

feat(auth)!: add login with passkeys, a blank line, a body explaining why, and BREAKING CHANGE: sessions now expire after 24 hours. Because of the !, a release tool would make this a major version.

Versions

Conventional Commits maps onto semantic versioning: fix to patch, feat to minor, and breaking changes to major. Work out what the next version number would be with the semver calculator.

How to use it

  1. Pick the type, such as feat or fix, and add an optional scope.
  2. Write a short description, and mark a breaking change if there is one.
  3. Add a body or footers if needed, then copy the message.

Privacy & limitations

Everything runs in your browser.

Related tools

SemverGitignoreLicense Generator

Frequently asked questions

What is the difference between feat and fix?

feat adds something users can use, and produces a minor release; fix corrects a bug, and produces a patch release.

When is a change breaking?

When existing users must change something to keep working: a removed option, a renamed function, or a different default.

Do I have to use Conventional Commits?

No, but tools such as semantic-release, release-please, and commitlint rely on it to automate version numbers and changelogs.

Free tool · runs in your browser · no account required