Conventional Commit Message Checker
Validate messages against chosen rules; explain failures; export a release grouping.
A clear result starts here
Add your input or try the worked example.
Using Conventional Commit Message Checker
Validate messages against chosen rules; explain failures; export a release grouping.
- Use Try example to explore conventional commit message checker, or enter your own commit subjects, one per line.
- Set allowed types, subject length reference. Read the field notes for supported values.
- Choose Review input and inspect the result, including any review flags or unsupported cases.
- Use the relevant download buttons to keep your result. CSV and report JSON preserve the available findings; original files are not changed.
Example
Commit subjects, one per line: feat(editor): add keyboard zoom fix: preserve empty folders feat!: remove old import format Update everything docs(readme): Allowed types: feat,fix,docs,refactor,test,chore Subject length reference: 72
Questions & answers
What does Conventional Commit Message Checker do?
Validate messages against chosen rules; explain failures; export a release grouping.
What input does this tool support?
Commit subjects, one per line. Allowed types. Subject length reference
What should I check before using the result?
Validates the Conventional Commits subject shape only. Full body/footer parsing and semantic-version release decisions remain outside this checker.
Can I keep or share the result?
Yes. Use the result-specific downloads, CSV where available and report JSON. Downloads can contain your supplied information, so review the content before sharing. Processing runs in this browser; public pages also include the site’s approved advertising and optional analytics.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.
