Awesome Reviewers checks + prompts

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.

V1004 technique
tactic Formatting and hygiene
not detectable from CI configuration

Sub-techniques

2

IDNameDescription
V1004.001Commit message lintEnforce a message convention so changelogs and release tooling can parse history.
V1004.002Pull request rulesFail or warn when a PR is too large, lacks a description, or touches files without matching tests or docs.

Craft 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.

Reverse engineer it

Signs that a codebase already runs this technique, and where to read how it is configured.

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

Open-source packages

2

Other techniques in Formatting and hygiene