Compare changes with the requested outcome
Start with the files, records, or pages the agent says it changed. Confirm each change supports the requested behavior, fits the existing design, and does not modify unrelated areas. Check names, links, translations, and edge cases that matter to the task.
When the work changes external resources, verify the result in the service itself rather than relying only on the agent's report. For code, inspect the diff and relevant generated output; for a message or configuration, confirm the saved version and target.
Resolve gaps before considering the task done
If a requirement is missing, identify the specific gap and continue from the current work rather than asking for a broad rewrite. Ask for evidence when an assertion depends on a build, route, or runtime behavior, and inspect the corresponding output.
Keep the review proportional to the impact: a wording change needs a content read, while a permissions or deletion change deserves a close target-and-effect check. Record any accepted trade-off so future edits have the right context.