Awesome Reviewers

Verification · Hygiene · Commit and pull request hygiene

Commit message lint

Enforce a message convention so changelogs and release tooling can parse history.

How to build it

  1. Add a commitlint config that sets the allowed types and scope rules.
  2. Install a commit-msg hook so non-conforming messages are rejected locally.
  3. Run the same check on every commit in pull requests in CI.

Signals in a repository

  • A commitlint.config.js or commitlint.config.ts at the repository root.
  • A commit-msg hook in the husky or pre-commit setup that runs commitlint.
  • Release tooling that reads commit types from history, such as release-please.

In practice

No scanned repository runs a tool for this check. The steps above are the only guidance.