Review changes read-only

Goal: an evidence-based review of current changes, without anything being modified. Skill: Review · Walkthrough: WT-05

1. Choose the scope

You want to review	Request
Uncommitted work	`Review my current workspace changes for correctness and authorization. Do not edit files or run build/test scripts.`
Unstaged only	`Review my unstaged changes; do not edit or run project scripts.`
Specific files	`Review src/auth/session.ts and its callers for token expiry handling.`
A commit range	`Review the changes in main..feature/export.` (the range must be accessible locally)

Without a supplied range, the agent reviews the current workspace. It explains exactly what was covered: staged, unstaged, and relevant untracked changes.

2. Read the findings

Each finding contains:

Classification: Confirmed defect, Plausible risk, or Improvement suggestion
Severity: CRITICAL · HIGH · MEDIUM · LOW · INFO
Confidence: HIGH · MEDIUM · LOW, with a stated basis
Location: an actual file and line, or an inspected range
Impact, and the requirement or control it relates to
Suggested fix and verification idea, both proposals only

A Plausible risk names the missing evidence that would confirm or dismiss it. It is never presented as an observed failure.

3. Verify it stayed read-only

git status --short

Nothing should have changed: no fixes, formatting, Memory updates, or report files. Tests stay NOT_RUN because Review never executes project code.

4. Act on findings

A found bug is not permission to fix it. To fix:

Select Implement.
Reference the finding: Fix the null-handling defect reported in the review at src/orders/export.ts:42; add a regression test.

To run tests as part of verification, use Test in run mode after the agent inspects the command and environment.

Want a report file?

Ask for it explicitly with a path. The analysis stays read-only; only that one output file is written.