Explain and inspect one exact change set with the user. Present one coherent slice at a time and wait for a decision before continuing.
This skill is read-only except for an authorized walkthrough log. A question or correction does not authorize code changes, commits, pushes, or publication.
Select the source
Confirm one source:
- the last completed change
- the working tree relative to
HEAD - a branch from its verified merge base to head
- a pull request from its verified base and head commits
Report working-tree changes outside the selected range. Do not silently include them.
Choose the presenter
Use the main thread for the normal interactive walkthrough. When the user requests an automated agent walkthrough, read presenter guidance and use a fresh read-only presenter.
Read presentation patterns before building the change map.
Walkthrough loop
- Inspect the selected diff, changed files, tests, documentation, and verification evidence.
- Build an ordered map that accounts for every changed file.
- Group files by behavior or contract rather than presenting a file dump.
- Present one slice with its behavior, decision, decisive evidence, verification, and risk. Include one lesson, a concrete example, and an exercise when the presentation patterns call for one.
- Ask one focused acceptance question.
- Pause for the user's response.
- Record a valid correction without implementing it.
- Rebuild affected slices after a separately authorized correction changes the range.
- Finish only when every changed file is covered and every correction is resolved or explicitly deferred.
Read walkthrough log guidance only when a log path is known or the user requests persistence. Update it at slice decisions and corrections, not for every message.
Finish
Summarize:
- covered behavior and files
- reviewer decisions and corrections
- verification evidence and limits
- unresolved risks or questions
Do not treat silence, a summary, a passing test, exercise completion, or presenter confidence as user acceptance.