Change Review
Inputs
Use the diff, intended behavior, affected callers, and test results. If the intent is missing, identify the smallest question that changes the review.
Workflow
- Trace changed inputs through callers and outputs. Read surrounding code before treating a surprising line as a defect.
- For each candidate finding, identify a concrete trigger, the resulting wrong behavior, and the smallest correction. Discard claims that depend on assumptions the code does not make.
- Check error handling, cleanup, retries, ordering, and compatibility with saved data where the diff touches them.
- Suggest a focused test at the lowest stable boundary. Separate a test you ran from one you recommend. Do not modify code during a review unless asked.
Deliverable
Lead with actionable findings ordered by impact. Each finding needs a location, trigger, consequence, and fix direction. If none are found, say so and name the meaningful limits of the review.


