Git Commit Message Linter

Checks your commit subject line against the Conventional Commits spec (type(scope): description), with exact pass/fail reasons for each rule.

Commit message (first line is the subject checked below)

Valid Conventional Commits format

Format checks (hard fail if broken)

Scope "(api)" is well-formed.

Type "feat" is a valid Conventional Commits type.

Exactly one space after the colon.

Description is present.

Style tips (informational, non-blocking)

Description starts lowercase.

No trailing period.

Subject line is 43 characters - within the ~72 char guideline.

Valid types

featfixdocsstylerefactorperftestbuildcichorerevert

Checks the Conventional Commits format of the subject (first) line only.

Was this tool helpful?

See this same kind of analysis applied to your whole repository

Call graphs, dead code, blast radius, and a health score. Results in 60 seconds, free.

Related tools

CODEOWNERS Generator

Path patterns to owners - valid CODEOWNERS file, bottom-to-top matching explained.

.gitattributes Generator

Line endings, language diff settings, Git LFS, and vendored paths in one file.

Git Hooks Generator

Pick a hook type and checks, get a working shell script plus install steps.

Branch Naming Convention Checker

Check a branch name against type/description, Jira-style, or kebab-case.

Squash vs Merge vs Rebase Explainer

What you care about to a recommended merge strategy, with the real tradeoffs shown.

Runs entirely in your browser. Nothing is stored. Free forever.