05 / Make review count
Read the change against the promise.
Review begins with the task, not the assistant summary. Restate the promised behavior, then inspect whether the patch delivers it without surprising its callers. Keep feedback specific enough to produce a small, verifiable follow-up.
Take two passes through the patch
First check scope: changed files, public interfaces, dependencies, and unrelated formatting. Then follow the behavior from input to output. A renamed variable is easy to see; an error that now disappears silently is easier to miss. Read the failure path and any state that survives between requests.
Close the loop with one clear correction
When you find a problem, describe the trigger, expected behavior, and observed behavior. "This loses the active filter after refresh" is more actionable than "make this robust." Have the assistant address that finding, inspect the follow-up diff, and rerun the check affected by the correction. Additional edits deserve additional review.
A starting prompt
Review finding: Invalid status values become active. Expected: Ignore unknown values and retain defaults. Please fix the parser boundary using its existing pattern. Add or update the relevant invalid-input check.