review-diff
Review diff
Reviews always run in subagents: a fresh context, on a different model from the implementer (which is probably you). Each subagent reviews through one lens: a file saying what to look for and how much code to read. You coordinate: scope, lenses, launch, check, triage, fix, report.
Other skills reuse this flow with their own lens set (for example, /deep-review).
1. Scope
The default change set is the working tree against the current branch's HEAD:
git diff HEAD plus untracked files (git status --short), which the diff doesn't show.
If that's empty (for example, a clean tree on a feature branch),
ask the user for the range, such as the merge-base with main.
Don't launch reviewers on an empty change set.
Find the originating ticket, task, or plan, if there is one, so lenses that judge against it can.