# Review a code change

Review [diff or pull request] against [intended behavior]. Use the relevant surrounding code to understand callers and state changes.

Prioritize defects introduced by the change: incorrect results, validation failures, data exposure, inaccessible interactions, and broken existing flows. For each actionable finding give the file and location, a concrete trigger, expected and observed behavior, and severity. Separate reproduced failures from plausible risks.

Use available tools to investigate a specific uncertainty. Do not invent a test run or assume a missing file behaves a particular way. If there are no evidenced findings, say so and record the limits of the review.

Return findings first, then any material verification gaps. Do not modify the code unless I ask for fixes.