Awesome Reviewers

Verification · Hygiene

Commit and pull request hygiene

Rules on the change itself rather than the code: commit message format, PR description, size limits, required labels or linked tickets.

Sub-techniques

  • Commit message lint V1004.001

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

  • Pull request rules V1004.002

    Fail or warn when a PR is too large, lacks a description, or touches files without matching tests or docs.

How to build it

  1. Write the rules you already enforce by hand in review as a Dangerfile or commitlint config.
  2. Start as warnings, then turn the rules people respect into failures.
  3. Keep size thresholds per directory, not global.

Signals in a repository

  • commitlint.config.js, a Dangerfile, or a PR title check in CI.
  • Release tooling that parses conventional commits (release-please, semantic-release).