Multi-Perspective Code Review

Perform a structured code review by examining changes from four independent constructive perspectives, synthesising their findings, then running an adversarial gap-analysis pass to catch what the constructive reviewers missed. Cross-check findings against source code and produce a unified report with actionable recommendations.

When to Use

• Before tagging a release
• Reviewing a large branch diff or PR
• Auditing a new subsystem (crypto, parsing, VM changes)
• When a single-perspective review would miss cross-cutting concerns

Background