Code Review

Two-stage code review: verify spec compliance FIRST, then assess code quality. Never reversed.

When to Use

• Reviewing pull requests or code submissions
• Validating implementation against requirements
• Providing structured feedback on code
• Ensuring spec compliance before quality assessment

Don't use for:

• General critical feedback on prompts/decisions (use critical-partner)
• Debugging errors (use systematic-debugging)

Critical Patterns