review

Review one change set and return a decision-led report.

Guardrails

• Review changes made on the currently checked-out branch.
• Do not implement or modify code.
• Do not commit, merge, push, or delete branches.
• Do not ask the user which branch to check against.
• Resolve the comparison base automatically from the repository default/base branch.
• Block approval if the current branch is behind the resolved comparison base; require sync + re-review.
• Do not update PRD tracking files here.
• Update tasks/context.md only for durable review outcomes.
• Examples: recurring risks, release-critical gotchas, or confirmed follow-up decisions.
• Do not invent test results; run checks or call out missing evidence.
• When asking for user decisions (e.g. scope clarification), provide numbered short-reply options (e.g. 1, 2, 3).