Git Commit Checker
Validate your commit messages against Conventional Commits and other conventions.
Valida il tuo commit message
Supporta messaggi multi-riga: usa la seconda riga vuota per separare il body.
Inserisci un commit message per avviare la validazione in tempo reale.
Come utilizzare Git Commit Linter
Choose a convention
Select conventional commits, Angular style or Gitmoji: changes the applied rule set and allowed types (feat, fix, docs, etc.).
Attach the commit message
Write or paste your message in the text field. Supports multi-line commits: header, empty line, body and footer (e.g. BREAKING CHANGE).
Read your score and rules
Validation is live: every modification recalculates percentage score and rule compliance list with error details for each.
Apply the correct suggestion
When available, use "Apply" to automatically replace the message with the correct version (period, lowercase, no space) or "Copy" to paste it elsewhere.
Suggerimenti
- Use "Incorrect Example" to quickly see which rules are violated most often and understand how to avoid them.
- Configure a Git hook (commit-msg) with Commitlint to apply these same rules automatically on every commit.
- Keep the first line under 72 characters: it's the recommended limit for optimal readability in git log --oneline.
Domande frequenti
What's the difference between conventional commits and Angular style?
Angular Style is a superset of Conventional Commits: uses the same format type(scope): description but adds the "release" type to allowed types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert). All other rules (line length, punctuation, lowercase) are identical.
What does it mean that a rule is "fixable"?
Rules with a "fixable" badge (e.g., period, lowercase, empty line before body, scope without spaces) can be automatically corrected in the "Suggested Corrected" box. Non-fixable rules (e.g., invalid type, malformed header) require manual rewriting.
How do you indicate a breaking change in a commit?
Be concise — keep similar length. In conventional commits and Angular style, you can use the exclamation mark after type/scope (e.g., feat!: or feat(auth)!:) or add BREAKING CHANGE: description in the footer, separated from the body by a blank line. The linter checks that at least one of these formats is present and correct.
Why is my Gitmoji failing the rule "no-conventional-mix"?
Be concise — keep similar length. The Gitmoji style expects the message to start with an emoji, not a type: description prefix. If your tool detects a pattern like "feat: description" without an initial emoji while you've selected the Gitmoji convention, report mixed styles: choose one style only for commits.
Is the commit message being sent to a server for validation?
No, all parsing and validation happens in JavaScript in the browser, no dependencies on npm or network calls: you can use it to validate commits containing sensitive information before pushing.