Awesome Reviewers

Verification · Hygiene · Commit and pull request hygiene

Pull request rules

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 a Dangerfile that reads PR size, description and labels from the event.
  2. Warn above the agreed size limit and fail when the description is empty.
  3. Require a test or docs file in the diff when source files under a listed path change.

Signals in a repository

  • A dangerfile.ts or dangerfile.js at the repository root.
  • A CI job that runs danger on pull_request events.

In practice

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