Code Review

This skill is guidance, not a script. Review the actual behavior and its evidence independently of the author's explanation. Report problems you can locate and explain; do not manufacture findings to fill a report.

When not to use

• Diagnosing a specific failure with an unclear cause. Use debug.
• Authoring the change rather than reviewing it.
• A pure style preference with no project rule behind it.

Inputs and authorization

• Required: the base, the target, and the requested scope. If the comparison or requirement is materially ambiguous, resolve it; do not invent a specification.
• Authorization: a review-only request produces findings, not edits or remote comments. Fix only when repair is already authorized.

Method

Establish the base, target, requirements, and applicable project standards. Include committed, staged, unstaged, and new files as the requested scope requires. Distinguish unrelated existing changes. Read removals, callers, configuration, and tests when they affect the result.