Paste a commit message and see where the format breaks
Conventional Commits is an agreement to write the first line of a commit message as type(scope)!: description. Paste a message as it is and this page checks the colon, the space, the description, the blank line and the footer tokens one at a time, then lists which items are violations. Everything you type is rendered as plain text, so tags inside a message show up literally.
The checks follow the Conventional Commits 1.0.0 specification: one space after the colon, a required description, a body and footers that begin after a single blank line, and footer tokens that use a hyphen in place of a space. For breaking changes, an exclamation mark before the colon and a BREAKING CHANGE footer carry the same meaning, and BREAKING CHANGE is written in capitals. Current as of October 2026.
Because the specification itself defines only feat and fix and the rest are conventions, a type outside that list is not counted as a violation. Length habits such as 50 characters for the first line are also not part of the specification, so they appear only as a note. This page checks and does not generate or rewrite messages, and scanning a whole commit history is not supported.
Frequently Asked Questions
No. The specification itself defines only feat and fix; the rest are widely used conventions. That is why a type outside the list is not counted as a violation here.
Either one is enough, since both signal a breaking change. Many projects use both anyway so that it is visible on the first line while the reason sits in the footer.
No. Length is a convention rather than a specification rule, so the first-line character count is shown only as a note and never counted as a violation.