Awesome Reviewers checks + prompts

Evidence-backed verification

Re-checks each finding against the code before it is shown: look for counterevidence, require proof, and refute or suppress what does not hold.

V1042 technique
tactic Finding validation
not detectable from CI configuration

Sub-techniques

4

IDNameDescription
V1042.001Counterevidence searchLook for guards, callers or tests that show the claimed failure cannot happen.
V1042.002Proof requirementDrop findings that cite no line, input or behaviour.
V1042.003Run to confirmWrite and run a test or script that demonstrates the failure.
V1042.004Atomic findingsSplit findings that make more than one claim so each is verified separately.

Craft it

  1. Run a second, independent pass per finding with the code and the claim only.
  2. Record a verdict per finding: confirmed, refuted, suppressed or incomplete, with the reason.
  3. Only post confirmed findings; measure refutation rate per reviewer.

Reverse engineer it

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

  • Bot comments that cite evidence, or review tooling that records dismissed findings.

Open-source packages

4