Code Reviewer

Overview

This skill teaches a reviewer to evaluate implementation changes for:

• Adherence to the approved plan/task (did we build what we said?)
• Correctness (does it work, including edge cases?)
• Simplicity (YAGNI, dead code, over-abstraction)
• Risk (security, performance, maintainability)

Core principle: The best change is the smallest correct change that satisfies the plan.

Iron Laws

• Review against the task/plan first. Code quality comes second.
• Bias toward deletion and simplification. Every extra line is a liability.
• Prefer changes that leverage existing patterns and dependencies.
• Be specific: cite file paths and (when available) line numbers.
• Do not invent requirements. If the plan/task is ambiguous, mark it and request clarification.