aw-review-quality-gatelisted

# Review Quality Gate Run this gate on every finding you have generated, **before** formatting output or delivering results. The gate catches false positives, noise, and miscalibrated severity — the most common failure modes of single-pass review. --- ## When to Use - After the reviewer agent generates findings (Step 2.5). - After DX or UX review skills produce their finding lists. - Any time a skill produces actionable recommendations that a human will read. --- ## Gate Checklist For **each finding**, answer every question. Be honest — a dropped false positive is worth more than a delivered one. | # | Question | Fail means | |---|----------|------------| | 1 | **Is it actionable?** The author can do something concrete. No "consider", "might want to", or "could be improved" without a specific fix. | Finding is vague noise | | 2 | **Did I read the surrounding code?** Not just the diff hunk — the full function, the caller, the guard clause three lines up. | Finding may be wrong | | 3 | **Is severity calibrated?** A style nit is never "required." A SQL injection is never "suggestion." Re-check the severity assignment against the actual impact. | Severity is misleading | | 4 | **Are file path and line number accurate?** Verify the cited location against actual file content. A finding pointing to the wrong line is worse than no finding. | Finding is unlocatable | | 5 | **Does this duplicate linter/formatter/type-checker output?** If the project's toolchain would catch this