Review

Review the intended change, not the entire software universe.

Entry

Default to read-only review. Modify code only when the user explicitly asks for fixes or the active workflow has already authorized remediation.

Understand intended behavior from the request/spec/plan and inspect the actual diff.
Determine which risk domains the diff truly touches. Compose only those specialist concerns.
Check correctness, compatibility, failure behavior, tests/evidence, and repository conventions at the affected boundaries.
Validate suspicious findings in surrounding code or direct evidence before reporting them.
Prioritize material, actionable findings. Distinguish blockers from improvements and avoid style churn already covered by automated tooling.

A green test suite is evidence, not proof that the implementation matches the intended contract.