Skip to content
>devspeak
← glossary
patternCommunication Patterns

Show me the diff

Ask the agent to show you exactly which lines it added, removed, or changed, so you see what it really did instead of trusting a summary.

a bit more technical

Request the line-by-line difference between the old and new code, for example with git diff, before accepting or committing a change. The diff is the ground truth; the agent's summary is only its description of it.

picture it

Asking for a tracked-changes version of a contract instead of the other side's summary of their edits. The summary might be honest, but the markup shows everything.

✗ instead of
ok looks good, commit it
✓ try
Before committing, show me the diff. Summarize each changed file in one line, and flag anything outside the header component we discussed.
why it matters

Agent summaries can leave things out: an extra file touched, a deleted check, a changed setting. Even if you can't read every line, the diff shows how much changed and where.

what your agent might say
agent
Here's the diff: 3 files changed, 12 lines added, 4 removed. The main change is in Header.tsx. I also updated one test to match.
how you might use it
you → your agent
Show me the diff before committing, and flag any change outside the files we discussed.
common mistake

Thinking you must understand every line for the diff to help. Just seeing which files changed, and by how much, reveals surprises.

builds on