Awesome Reviewers

Verification · Code review · Review question checklists

Behavioural questions

Questions about what changes for users and callers.

How to build it

  1. Ask what changes for end users once the change ships.
  2. Ask which callers see a different return value, error or default.
  3. Ask whether the change needs a changelog entry or a migration note.

Signals in a repository

  • A pull request template section for user-visible or breaking changes.
  • CHANGELOG.md entries or migration notes added in the same pull requests.

In practice

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