Conventional Commit Linter (commitlint Rules in the Browser)
Paste one or more commit messages and see which commitlint conventional rules they break, with error and warning levels like the real tool.
Use the tool
Why this tool exists
Commit linting usually runs in a git hook after you install node packages. Sometimes you just want to check a message, a pull request title or a squash commit before it goes in, without a config file.
This page applies the default rules of the conventional config: allowed types, lower-case type, no full stop, header length, blank lines and line length. The subject-case check is an approximation, and custom rules from your own commitlint config are not read.
How to use it
- Paste a message, or several separated by a line with three dashes.
- Adjust the allowed types and length limits if your team differs.
- Read the error and warning lines for each message.
- Fix the message and paste it again.
Frequently asked questions
Is this the same as running commitlint?
It follows the default rules of the conventional config, which I read from its source. Your own config, plugins and ignores are not applied, so treat it as a quick check.
What is the difference between error and warning?
Errors fail the commit in commitlint. Warnings are reported but do not fail it. Blank-line rules are warnings by default.
Why is a capital letter in the subject reported?
The default config forbids sentence-case, start-case, pascal-case and upper-case subjects. This tool flags a leading capital letter as an approximation.
Is my message sent anywhere?
No. Everything is checked in your browser.