Awesome Reviewers

Verification · Code review

Logic and correctness review

Reads the change for wrong behaviour: off-by-one, inverted conditions, missed error paths, broken invariants, race conditions.

Sub-techniques

  • Logic bug review V1035.001

    Look for conditions, loops and state transitions that do not match intent.

  • Error path review V1035.002

    Check failures, retries and partial writes.

  • Type and contract consistency V1035.003

    Check that values crossing module boundaries keep their meaning.

How to build it

  1. Give the reviewer the intent, the diff and retrieved context.
  2. Ask for findings only with a concrete triggering input or state.
  3. Validate each finding before posting (see Finding validation).

Signals in a repository

  • Review bot workflows (claude-code-action, pr-agent) and their prompt files.