Git & Version Control
Git Commit Message Validator
Paste a commit message to validate type, scope, subject length, breaking change syntax, and footer format against Conventional Commits 1.0.
No data is transmitted — everything runs locallyTool
About this tool
Git Commit Message Validator
The Git Commit Message Validator checks Conventional Commits 1.0 format, subject line length, imperative mood, breaking change syntax, and issue reference footers.
• Validate a commit before pushing to avoid CI lint failures
• Check breaking change footer syntax for a major version bump
• Verify commit format before configuring semantic-release
• Lint commits from a rebase session before opening a PR
Affiliate disclosure
Credential and secrets management for teams. 1Password provides enterprise password management and secrets infrastructure for development teams.
View git credentials with 1Password
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Git Commit Message Validator checks Conventional Commits 1.0 format, subject line length, imperative mood, breaking change syntax, and issue reference footers.
What affects the result most?
Conventional Commits 1.0: type(scope): description — type must be feat/fix/docs/chore/refactor/test/ci/perf/build. Subject line 72-char limit — wraps in git log --oneline and GitHub commit list views. Imperative mood: 'Add feature' not 'Added' or 'Adds' — matches git revert message style.
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.