Deep Review

Perform thorough code review using three perspectives with opposing mindsets. Their disagreement surfaces issues; their agreement signals confidence.

When to Use

• Architectural changes, multi-file refactors, or security-sensitive code
• PRs that are too important for single-pass review
• When you suspect confirmation bias in a standard review
• High-stakes merges where the cost of a missed issue is high

When NOT to Use

• Routine single-file edits (use standard code-review skill)
• Documentation-only PRs
• Formatting/linting changes