Walkthrough

Produce one continuous, readable document that walks the user through a change in a logical order — not the alphabetical order their editor shows. The user reads it top to bottom and builds understanding as they go.

Resolve scope

From the argument:

• No argument → git diff HEAD (working tree vs HEAD — staged + unstaged combined; matches the VS Code Git tab).
• A commit ref (HEAD, HEAD~2, abc123, main, etc.) → git show <ref>.
• A range (a..b or a...b) → git diff <range>.
• branch → current branch vs its merge-base with main (fall back to master if main doesn't exist): git diff $(git merge-base HEAD main)...HEAD.

If the argument is ambiguous (could be a branch name or a file path, etc.), ask before running.

Gather

1. git diff --stat <scope> — file list and line counts.
2. git diff <scope> — full content. For commits use git show <ref> instead.