Developer Experience
Git Commit Message Linter
Paste a commit message to validate Conventional Commits format, subject line length, imperative mood, breaking change syntax, and semantic versioning trigger.
No data is transmitted — everything runs locallyTool
About this tool
Git Commit Message Linter
The Git Commit Message Linter validates Conventional Commits 1.0 format including type, scope, subject length, body format, breaking change footers, and semantic versioning triggers.
• Validate a commit message before pushing to avoid CI lint failures
• Check that a breaking change is correctly flagged for a major version bump
• Verify commit message format before configuring semantic-release in CI
• Lint commit messages from a rebase session before opening a PR
Affiliate disclosure
Uptime, incident, and on-call management. Better Stack provides status pages, incident management, and on-call scheduling for engineering teams.
View options with Better Stack
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Git Commit Message Linter validates Conventional Commits 1.0 format including type, scope, subject length, body format, breaking change footers, and semantic versioning triggers.
What affects the result most?
Conventional Commits format: type(scope): description — type must be one of feat/fix/docs/style/refactor/test/chore/ci/perf/build. Subject line length: 72 characters max — wraps in git log --oneline and GitHub commit views. Imperative mood: 'Add feature' not 'Added feature' or 'Adds feature'.
How should I use the result?
Treat the tool's output as a first-pass check, not a proof of correctness. A clean pass means no issues in the patterns this tool recognizes; a failure points to a specific problem you can investigate in your source. The underlying spec is the authoritative source for edge cases.
Related tools