Trace the affected path
Find the entry point and follow the changed data through its callers. Check whether the implementation handles absent values, errors, and repeated operations consistently. Look for unrelated edits that make the result harder to assess. Ask for a smaller patch when a narrow fix has grown into several independent changes.
Read the evidence precisely
Distinguish a test that ran from a test the assistant merely suggested. Inspect the result and confirm that the relevant behavior was exercised. A check that imports a module does not prove that its error recovery works. Prefer a focused regression case for the reported defect over assertions that simply restate the implementation.
End with an actionable decision
Record concrete defects with their trigger, impact, and location. Separate blockers from optional polish. When a check cannot run, state the remaining uncertainty and what would resolve it. Accepting a change is a judgment based on its behavior and evidence, not a reward for how confidently the assistant describes its own work.
