Review Changes

Orchestrate the full review pipeline: handoff → review → fix. This skill chains three phases with user checkpoints between each.

Phase 0: Read Workspace Context

Before starting the review, check for workspace context assembled by the Chalk extension:

1. Read .chalk/context/review-changes.md if it exists. This contains:
   • Current git state (branch, uncommitted changes, recent commits)
   • Active diagnostics (lint/type errors already flagged by the IDE)
   • Latest test results (pass/fail counts, failing test names)
   • Recently edited files (what the developer has been working on)
2. If the context file doesn't exist, proceed without it — the skill works standalone.
3. Use context to prioritize review focus:
   • If there are existing diagnostics errors, address those first
   • If tests are failing, flag test-related changes as high priority
   • If recently edited files don't match the diff, note potential forgotten files