code-reviewlisted

<!-- intentional divergence from Supervisor: Edition omits the two Supervisor-specific checklist items ("every export called by production", "filter-style guards have test data") that reference Supervisor-only mutation-testing skill. Heirs don't ship mutation-testing. Audited 2026-05-31. --> # Code Review Skill > Good reviews catch bugs. Great reviews teach the author something. ## Review Priority (What Matters Most) 1. **Correctness** — Does it do what it's supposed to? 2. **Security** — Can it be exploited? 3. **Maintainability** — Will the next person understand this? 4. **Performance** — Will it scale? 5. **Style** — Is it consistent? (ideally enforced by linters, not humans) ## 3-Pass Review | Pass | Focus | What You're Looking For | Time | | ---- | ----- | ----------------------- | ---- | | 1. Orientation | Big picture | Does the approach make sense? Is the scope right? Over-engineered? | 2-3 min | | 2. Logic | Deep read | Edge cases, null handling, error paths, concurrency, off-by-one | 10-15 min | | 3. Polish | Surface | Naming, duplication, test coverage, docs | 3-5 min | **Pass 1 shortcut**: Read the PR description and test names first. They reveal intent faster than code. ## Comment Prefixes | Prefix | Meaning | Author Response | | ------ | ------- | --------------- | | `[blocking]` | Must fix before merge | Fix it | | `[suggestion]` | Better approach exists | Consider it, explain if declining | | `[question]` | I don't understand | Clarify (in code, not j