Conventional Commit Linter
Check a commit message against the Conventional Commits format and see exactly what to fix.
- Type
- feat
- Scope
- api
- Breaking
- no
- Footers
- 1
Allowed types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
How to use
Paste the commit message, including any body and footers.
Read the problems and warnings listed under the status line.
Edit the message until it passes, then use it with git commit.
Example
A message that needs a fix
Without a type and colon the message cannot be parsed. Try "feat(auth): add login page".
Added login page.
The first line must look like "type(scope): subject".
Frequently Asked Questions
feat, fix, docs, style, refactor, perf, test, build, ci, chore and revert. These are the common set used by most commit linters.
Capabilities
- Type and scope checks
- Breaking change detection ("!" and footer)
- Header length limit you can change
- Blank-line and trailing-period rules
- Parsed fields shown
Related Tools
Bump a version by major, minor, patch or pre-release and compare two versions using SemVer rules.
Quickly find common Git commands and build tailored .gitignore templates for your projects.
Compile semantic release notes grouped by Added, Changed, Deprecated, and Fixed.
Craft clear, reviewer-friendly PR summaries with test plans and breaking change warnings.
Explore
Connected career roadmaps, algorithmic problems, and real-world curricula related to Conventional Commit Linter.
Clear, milestone-driven paths from first fundamentals to your target engineering role.
Backend Engineer / Distributed Systems Developer · 8-12 months
Full-Stack Software Engineer · 8-12 months
DevOps / Cloud Infrastructure Engineer · 8-12 months
Cybersecurity Analyst / AppSec Engineer · 8-12 months