Code Review

Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses.

When to Use

• After implementing a feature or fixing a bug
• Before creating pull requests
• When receiving feedback from reviewers
• Before claiming any task as complete
• When stuck on a problem and need a second opinion

Workflow

Step 1: Scout edge cases — invoke /scout with edge-case-focused prompt Step 2: Request review — dispatch code-reviewer subagent with SHAs Step 3: Address findings — fix Critical immediately, Important before proceeding Step 4: Verify — run verification gates before claiming done