What problem does it solve?
Code review helps catch issues early, ensuring correctness, security, performance, and maintainability before shipping. It supports a systematic review process that emphasizes evidence over guesswork.
Core Features & Use Cases
- Structured, evidence-based review process covering correctness, security, performance, and maintainability.
- The Iron Law: NO MERGE WITHOUT REVIEW. NO REVIEW WITHOUT EVIDENCE.
- When to Use: Mandatory checks before merging to main/production, after major features, after each task in a plan, and before deploy; Optional checks when stuck, before refactoring, after fixing complex bugs, or when learning a new codebase.
- When NOT to Use: Avoid reviewing auto-generated diffs without verifying outputs; skip trivial one-character fixes.
- Anti-Shortcut Rules & Iron Questions: Guidelines to avoid rubber-stamping and to probe edge cases and security considerations.
- The Review Process: A structured sequence from context understanding to detailed checks ensuring correctness, security, performance, and maintainability.
Quick Start
Apply the structured checklist to the current change set to identify issues and provide actionable feedback before merging.