Lite Review

Goal

A short list of findings a senior engineer would hold the merge for. Three questions drive every finding:

1. Does this code do what it says, clearly?
2. What can be deleted, consolidated, or refactored away?
3. What edge case slips through?

Precision over coverage: three real problems beat thirty nits. The run is read-only until the user approves fixes.

Scope

From the argument, settle exactly what "the changes" are. Three target shapes:

• PR — gh pr diff <n>; on a forge gh does not serve, the forge tool the project names, else the branch diff against the PR's base. BASE = the merge-base with the PR's base branch. Ask before reviewing local commits the PR's head lacks. Don't re-raise what the PR's existing review threads settled.
• Commit range / branch vs main — git diff main...HEAD (three-dot, so unrelated main commits stay out of the diff). A given range like A..B works too.
• Uncommitted — git diff HEAD, plus untracked files from git status --short read in full — git diff never shows them.