Code Review

Review the requested change and the connected behavior it can break. Correctness, security, data integrity, and compatibility take priority over shortening code. Review-only unless the user asks for fixes.

1. Establish Scope and Evidence

• Honor an explicit target first: staged, uncommitted, commit, branch/base, PR, or named files. Unrelated dirty files do not change that target.
• Without a target, use staged + unstaged + untracked changes when dirty. Otherwise use the branch diff from its actual PR/tracking base; if unavailable, resolve origin/HEAD, then main/master. Use merge-base comparison for branch reviews. If the result is empty or the base ambiguous, say so; do not silently review an arbitrary commit.
• For staged/commit/PR reviews, read source at that target revision (index for staged), not a newer working-tree version. Checks run against a different state are explicitly limited evidence; use an isolated snapshot when exact-state execution is needed, preserving user changes.
• Read the diff, then trace changed contracts through callers, callees, types, config, exports, and tests. Expand only where a reachable dependency can affect the result; do not audit the whole repository.
• Establish relevant runtime assumptions from deployment/config/docs: process count, input sizes, trust boundaries, persistence. Label unknowns; do not invent scale requirements.
• Use targeted searches and source ranges. Reuse evidence already in context; inspect the final changed state after fixes. Do not load other review skills merely because they are installed.

2. Review the Applicable Risks

Completeness: map each requested requirement to behavior. Block silent omissions, unauthorized scope cuts, and stubs for current requirements. A TODO or workaround comment alone is not a defect; verify what remains unimplemented and whether deferral was agreed.

Correctness and compatibility: trace inputs to outputs and side effects. Check changed return/error contracts, persisted formats, migrations, partial failures, and affected callers. A local fix must not leave the same root cause reachable elsewhere.