code-reviewlisted

# Code Review Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses. ## Overview Code review requires four 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 4. **Security & compatibility awareness** — Recognize when a change warrants security or API compat review 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. **Fix everything you see — pre-existing or not.** When a review surfaces an issue, fix it regardless of whether the current diff introduced it. "Not my change" is not a reason to leave broken code in place. Every finding gets fixed before the PR merges. ## 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 refacto