Smart Validation

Commit MessageLinter

Write perfect commit messages following Conventional Commits and industry standards.

Real-time Validation

Instant feedback as you type your commit message

Best Practices

Follow Conventional Commits specification

Smart Suggestions

Get helpful tips to improve your messages

Commit Validator

Validate Your Commit Message

Get instant feedback and improve your commit messages

Commit Message

0/72 characters • 1 line(s)

Start typing your commit message

Real-time validation will appear as you type

Conventional Commits

Commit Types Reference

Standard commit types with examples

feat

A new feature for the user

feat(auth): add OAuth2 authentication

fix

A bug fix for the user

fix(api): resolve timeout issue

docs

Documentation changes

docs(readme): update installation steps

style

Code style changes (formatting, etc)

style: format code with prettier

refactor

Code refactoring

refactor(utils): simplify date formatting

test

Adding or updating tests

test(auth): add unit tests for login

chore

Maintenance tasks

chore: update dependencies

perf

Performance improvements

perf(db): optimize query performance

Best Practices

Do's and Don'ts

Follow these guidelines for better commit messages

Do

Use imperative mood: "add feature" not "added feature"
Keep first line under 72 characters
Start with lowercase after type
Use present tense
Include scope when applicable: feat(auth):
Add body for complex changes

Don't

Don't end subject with period
Don't use past tense
Don't be vague: avoid "fix stuff"
Don't include multiple changes in one commit
Don't use uppercase in subject
Don't exceed 72 characters in first line