code-review

# Code Review Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses. ## Overview Code review requires three distinct practices: 1. **Receiving feedback** - Technical evaluation over performative agreement 2. **Requesting reviews** - Systematic review via code-reviewer subagent 3. **Verification gates** - Evidence before any completion claims Each practice has specific triggers and protocols detailed in reference files. ## Core Principle **Technical correctness over social comfort.** Verify before implementing. Ask before assuming. Evidence before claims. ## When to Use This Skill ### Receiving Feedback Trigger when: - Receiving code review comments from any source - Feedback seems unclear or technically questionable - Multiple review items need prioritization - External reviewer lacks full context - Suggestion conflicts with existing decisions **Reference:** `references/code-review-reception.md` ### Requesting Review Trigger when: - Completing tasks in subagent-driven development (after EACH task) - Finishing major features or refactors - Before merging to main branch - Stuck and need fresh perspective - After fixing complex bugs **Reference:** `references/requesting-code-review.md` ### Verification Gates Trigger when: - About to claim tests pass, build succeeds, or work is complete - Before committing, pushing, or creating PRs - Moving to next task - Any statement suggesting success/co...