Unified Review — Common Mistakes

Skipping graph context — always run get_minimal_context first; CRG context is what makes the review token-efficient and blast-radius aware.
Rushing to fix — this skill is READ-ONLY. Present findings, wait for user decision. Never apply fixes, commit, or push.
Ignoring tier — read .code-review.yaml. fast skips Layer 2/3; strict requires per-item confirmation for every blocker/major.
Judging metrics without evidence — score_review_tool outputs are heuristics. Cite the evidence, and let the LLM confirm SQL/exception/vuln findings before presenting them as facts.
Missing manual-review modules — payment, order, inventory, permission, distributed-lock, data-migration always require a manual review checklist.
Forgetting enum completeness reads OUTSIDE the diff — grep sibling values, then read each consumer; in-diff review alone is insufficient.
Batch-skipping blockers — 🔴 blockers cannot be batch-skipped; each needs an explicit user decision.
Not producing the report — always call generate_report_tool at the end and present the text report inline.