Review

Find the change from $ARGUMENTS or the conversation. Ask if unclear. If REVIEW.md exists at the repo root, follow it. Flag pre-existing problems only if the change reaches or worsens them. Do not fix anything.

Review to disprove, not confirm. Treat confident prose as non-evidence; verify behavior from code and tests.

Quality

Check task behavior, edge cases, failure paths, security boundaries, contracts, and existing patterns. Check whether tests prove changed behavior. Flag dead code left by the change: unused variables, compatibility shims with no consumers, and comments narrating removed code.

Complexity And Over-Engineering

Flag new dependencies when the project already has a way to do the same thing, hand-rolled code covered by the standard library or platform, abstractions with one implementation, config nobody sets, and wrappers that only delegate.

For complexity findings, name what to cut and what replaces it: existing helper, standard library function, platform feature, simpler local code, or nothing.

Findings

List findings: blockers, important, then nits. For each finding, include location, severity, bug, impact, and fix direction when it changes the next action.