What it means
The UI renders before/after (or add/remove) views of proposed edits, often with per-hunk Accept/Reject and a summary of files touched.
Why designers should care
Designers reviewing agent-generated UI or content need readable diffs, not raw git output, grouped by file, with plain labels and undo after apply.
Example
Cursor shows agent file edits in a side-by-side diff; the user accepts two hunks in App.tsx, rejects a third, and the agent continues with only approved changes applied.
Common mistakes
- Apply-all with no per-hunk control on multi-file agent runs.
- Diffs that hide non-code changes designers care about (copy, spacing tokens).
- No undo after accept, forcing manual revert when one hunk was wrong.
Frequently asked questions
What is Diff / Patch Review?
Diff or patch review is the UX pattern where users inspect line-by-line changes an agent proposed, code, copy, config, and accept or reject each hunk before apply.
Why should designers care about Diff / Patch Review?
Designers reviewing agent-generated UI or content need readable diffs, not raw git output, grouped by file, with plain labels and undo after apply.
What are common mistakes with Diff / Patch Review?
Apply-all with no per-hunk control on multi-file agent runs; Diffs that hide non-code changes designers care about (copy, spacing tokens); No undo after accept, forcing manual revert when one hunk was wrong.