Code Review Report

Build a single-file HTML report a reviewer reads before digging through the raw diff. A diff shows what changed; it doesn't show why, what was rejected, or what's still missing. Filling that gap with the context accumulated in this conversation is what separates this from a diff viewer.

1. Collect the change

Check the change with git status and git diff. Default scope: current branch vs the default branch, plus the uncommitted working tree.

• git diff <base>...HEAD (committed), git diff HEAD (uncommitted)
• Untracked files don't appear in diffs — find them with git status and read them directly.

If the scope is mixed or contains unrelated changes, ask the user. Exclude unrelated changes or mark them separately.

2. Collect the working context

Gather from this conversation the things a diff never records: