review-difflisted

# Review Diff ## When to use this skill Invoke this skill when: - A task's status is `IN_REVIEW` and you (as the Reviewer) are picking it up. - You have access to the diff for the work — either the working tree, the staged changes, or the diff against a base branch (depending on how the task was scoped). - You can run the project's tests and lint. **Do not use this skill** to review tasks that aren't yet `IN_REVIEW`, or to edit code directly. The Reviewer proposes; the Coder implements. ## Instructions You are walking a diff and deciding whether the task can move to `VALIDATED`. Hold the work to three contracts: (1) the subtask acceptance criteria, (2) `governance.md`, (3) baseline code quality. ### Procedure 1. **Read the contract.** Read `tasks/active/{ID}/TASK details {ID}.md` — identify every subtask's acceptance criterion. Read `tasks/active/{ID}/TASK {ID}.md` — note every recorded permission approval. 2. **Get the diff.** Determine the diff scope from the task (working tree / staged / branch diff). Use `git diff` for the appropriate range. 3. **Run tests and lint.** Whatever the project's standard commands are. Capture pass/fail and coverage of the acceptance criteria. 4. **Acceptance pass.** For each subtask, find the change in the diff that demonstrates the criterion. Note any criterion that lacks a corresponding change — that's a `blocker` finding. 5. **Governance pass.** Scan the diff for actions whose risk level is HIGH or CRITICAL per `governance.md` (migr