Conventional commit checker
Check a Conventional Commit message and its declared release impact. Review header, body and breaking-change footer issues.
Conventional Commits 1.0 structure and explicit impact rules. No repository access or automatic version bump. Runs on your device with no configuration, repository or credential lookups. Up to 1,000,000 input characters and 4,000,000 characters per output file. Paste text to process locally. Review the supported syntax and the result before downloading. Results update as you type. Up to 1,000,000 characters.
Your result
How to use Conventional commit checker
- Paste one complete commit message.
- Review format issues and the declared release impact.
- Download the parsed report or use accepted messages in the changelog generator.
Useful next steps
Check one complete commit message
Paste the header and any body or footers. The expected shape is type(scope)!: description, with scope and ! optional. A blank line separates the header from the body or footers. Custom types are allowed; this does not enforce a team-specific type allowlist.
See the impact declared by the message
feat suggests a minor change, fix suggests a patch, and ! or a BREAKING CHANGE footer suggests a major change. A breaking-change footer takes precedence. Other types have no automatic version impact here.
Review meaning before making a release
The tool checks message structure, not the code behind it. A commit can have valid syntax and still misdescribe its change. Project release rules, pre-1.0 policy and version selection remain a human decision. The downloadable report includes the parsed message you supplied.