Watch the explanation. Practice the skill.
Give coding assistants bounded context and inspect the diff
Give a coding assistant a narrow change and inspect what it actually changed.
Captions appear here during playback.
Give coding assistants bounded context and inspect the diff
Give a coding assistant a narrow change and inspect what it actually changed.
Video playback is unavailable. Read the descriptive transcript below, go directly to practice, or open the video file.
Source-based teaching example · Fictional data · Reviewed 2026-10-03. Microsoft Mark · locally synthesized. On a small screen, use fullscreen for diagram details or read the transcript.
Read the descriptive transcript
0:00 · What you will learn
Give a coding assistant a narrow change and inspect what it actually changed.
What appears on screen
Give a coding assistant a narrow change and inspect what it actually changed.
0:07 · The idea
Specify allowed files and forbidden actions. Read the diff before accepting it. Run the relevant checks yourself or report that they were not run.
What appears on screen
Specify allowed files and forbidden actions. Read the diff before accepting it. Run the relevant checks yourself or report that they were not run.
0:19 · One useful term
Diff. A comparison showing what changed between versions of files.
What appears on screen
A comparison showing what changed between versions of files.
0:27 · A worked example
The request permits only a starter-code validation fix. The proposed diff also changes a release setting and claims tests passed without output. Reject the unrelated change and request a scoped patch.
What appears on screen
The request permits only a starter-code validation fix. The proposed diff also changes a release setting and claims tests passed without output. Reject the unrelated change and request a scoped patch.
0:43 · Your turn to think
Does “tests passed” establish execution without a command or result? Pause and decide before continuing.
What appears on screen
Does “tests passed” establish execution without a command or result? Pause the video if you need more time.
1:01 · Why this answer works
No. Record observed commands and outputs. An unrun patch is an unexecuted proposal.
What appears on screen
No. Record observed commands and outputs. An unrun patch is an unexecuted proposal.
1:10 · Check 1
Inspect every changed file.
What appears on screen
Inspect every changed file.
1:15 · Check 2
Test valid and invalid inputs.
What appears on screen
Test valid and invalid inputs.
1:21 · Check 3
Distinguish observed execution from a claim.
What appears on screen
Distinguish observed execution from a claim.
1:26 · Now try a different case
Open the lesson and try its different practice case. Use every check in the full task. Watching alone does not mark the lesson complete.
What appears on screen
Open the lesson Try the new case Check and revise The full task and its requirements are in the linked lesson.
Watching explains the example. Complete the lesson practice to check what you can do. Explore all visual lessons →