Free developer tool

Free Conventional Commits Generator & Linter

Conventional Commits is a commit message format, type(scope): description, that release tools read to build changelogs and pick the next version. This generator writes a valid message and the matching git commit command, the linter checks any message against the same rules as commitlint's conventional preset, and both show the SemVer bump the commit would trigger. Everything runs in your browser.

Build a commit message

A new feature. Example: feat(auth): add magic link sign-in

Header: 34 / 72 characters. Use the imperative mood, lowercase, no period.

✓ Valid Conventional Commit. No problems found.

SemVer bump: Minor (new feature) · 1.4.2 → 1.5.0

Commit message

feat(auth): add magic link sign-in

Users can request a one-time sign-in link by email instead of typing a
password.

Closes #42

git commit command

git commit -m 'feat(auth): add magic link sign-in' -m 'Users can request a one-time sign-in link by email instead of typing a
password.' -m 'Closes #42'

Lint an existing commit message

Paste a message from git log or a pull request title. Lines that start with # are ignored, as git does.

  • ✖ type-case: Write the type in lowercase: "fix", not "Fix".
  • ⚠ scope-case: Most teams write the scope in lowercase: "(login)".
  • ✖ subject-full-stop: Remove the period at the end of the description.
  • ✖ subject-case: Start the description with a lowercase letter: "fixed".
  • ⚠ subject-imperative: Use the imperative mood: "fix", not "Fixed" (write it as a command, like "fix login page").
  • ⚠ body-leading-blank: Leave a blank line between the header and the body.
  • ⚠ footer-leading-blank: Leave a blank line between the body and the footers.
  • ✖ breaking-change-token: Write the footer token exactly as "BREAKING CHANGE: " (uppercase, then a colon and a space). Release tools ignore other spellings, so the major version bump would be missed.
Type
Fix
Scope
Login
Breaking
no
Footers
(none)

SemVer bump: Patch (fix) · 1.4.2 → 1.4.3

Suggested fix

fix(login): fix redirect loop after OAuth

The callback ignored the state param.

BREAKING CHANGE: /login now requires ?next=

Conventional Commits types cheat sheet

TypeUse it forExampleBump
featA new featurefeat(auth): add magic link sign-inminor
fixA bug fixfix(cart): keep coupon after page reloadpatch
docsDocumentation only changesdocs: explain the release workflownone
styleFormatting, white-space or semicolons; no change in meaningstyle: apply prettier to the api foldernone
refactorA code change that neither fixes a bug nor adds a featurerefactor(db): extract query buildernone
perfA code change that improves performanceperf(search): cache tokenized queriespatch
testAdding missing tests or correcting existing teststest(auth): cover expired tokensnone
buildChanges to the build system or external dependenciesbuild(deps): bump next to 16.4.2none
ciChanges to CI configuration files and scriptsci: cache pnpm store in GitHub Actionsnone
choreOther changes that don't modify source or test fileschore: update .gitignorenone
revertReverts a previous commitrevert: feat(auth): add magic link sign-inpatch

Any type with ! or a BREAKING CHANGE: footer bumps the major version.

Commit message format, line by line

feat(auth)!: add magic link sign-in     <- header: type(scope)!: description

Users can request a one-time sign-in    <- body: what and why, wrapped at 72
link by email instead of a password.

BREAKING CHANGE: /login needs ?next=    <- footers: token: value or token #value
Closes #42

How to write a Conventional Commit

  1. 1. Pick a type and scope

    Choose feat, fix, docs or another type, then an optional scope that names the area you changed, such as api or ui.

  2. 2. Write the description

    Write a short, lowercase, imperative description with no period, ideally under 72 characters for the whole header.

  3. 3. Add a body and footers

    Explain why in the body, tick Breaking change to add ! and a BREAKING CHANGE footer, and list issues to close.

  4. 4. Copy and commit

    Copy the message or the git commit command. Paste older messages into the linter to check them and get a fixed version.

Enforce Conventional Commits with commitlint and husky

These commands add a commit-msg hook that rejects messages that break the rules, the same rules this linter checks. Run them in the repository root of a Node project.

npm install --save-dev @commitlint/cli @commitlint/config-conventional husky
echo "export default { extends: ['@commitlint/config-conventional'] };" > commitlint.config.js
npx husky init
echo "npx --no -- commitlint --edit \$1" > .husky/commit-msg

Conventional Commits FAQ

What are Conventional Commits?

Conventional Commits is a specification for commit messages: type(scope): description, an optional body, and optional footers. The fixed format lets tools such as semantic-release, release-please and commitlint generate changelogs, pick the next version number and reject malformed messages.

What is the Conventional Commits format?

The header is type, an optional scope in parentheses, an optional ! for a breaking change, a colon, one space and a short description, for example feat(api): add pagination. A blank line separates the header from the body, and another blank line comes before footers such as BREAKING CHANGE: or Closes #42.

Which commit types can I use?

The spec requires only feat and fix. The widely used @commitlint/config-conventional preset also allows build, chore, ci, docs, perf, refactor, revert, style and test. Types are lowercase.

How do I mark a breaking change?

Add ! before the colon, as in feat(api)!: remove v1 endpoints, or add a footer that starts with BREAKING CHANGE: followed by what breaks. Either one triggers a major version bump. The footer token must be uppercase.

Which version bump does a commit trigger?

With semantic-release defaults, a breaking change bumps the major version, feat bumps the minor version, and fix, perf and revert bump the patch version. docs, style, refactor, test, build, ci and chore do not cause a release on their own.

Should the description start with a capital letter?

No. commitlint's conventional preset rejects descriptions in sentence case, start case or all capitals, and a trailing period. Write it in the imperative mood, like a command: fix login redirect, not Fixed login redirect.

Let your AI agent commit the right way

Tornic runs deterministic multi-step workflows on the Claude Code, Codex or Cursor CLI you already pay for, including the test, commit and release steps around the code.

Explore Tornic

Related free tools