Agents must prioritize findings in this order and report them in this order when multiple issues are present:
- Correctness (behavioral bugs, warnings, broken contracts, stale state, invalid keys)
- Maintainability (dead code, duplication, unnecessary complexity, high-review-cost risks)
- Style (formatting/convention consistency that does not change behavior)
Do not prioritize Style-only findings ahead of unresolved Correctness or Maintainability findings.
For every rule below, agents should provide:
- Evidence: exact code snippet or file/line reference from the changed code
- Category: the rule's listed primary category (Correctness, Maintainability, or Style)
- Confidence: apply the rule's confidence threshold before escalating severity in review feedback
- Exceptions: check the rule's false-positive section before flagging