Awesome Reviewers checks + prompts

Noise budget

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

V1048 technique
tactic Finding validation
not detectable from CI configuration

Sub-techniques

2

IDNameDescription
V1048.001Volume capAt most N comments per review, highest severity first.
V1048.002Carried findingsFindings that did not fit are kept and offered on the next run instead of dropped.

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

Reverse engineer it

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

  • Review bot config with a maximum comment count.

Open-source packages

2