Awesome Reviewers

Verification · Finding validation

Noise budget

A fixed cap on how many findings are posted per change, filled in severity order, so the important ones are read.

Sub-techniques

  • Volume cap V1048.001

    At most N comments per review, highest severity first.

  • Carried findings V1048.002

    Findings that did not fit are kept and offered on the next run instead of dropped.

How to build it

  1. Set the cap from how many comments reviewers actually address.
  2. Sort by severity, then certainty.
  3. Store the overflow and resurface it when the budget allows.

Signals in a repository

  • Review bot config with a maximum comment count.