---
description: Run LazyClaude 5-lane review discipline.
argument-hint: '<scope>'
---

Use the `review-work` skill for the user's current scope or command arguments.

Run the 5-lane review contract: goal and constraint verification
(goal/constraint), hands-on QA execution, code quality review, security review,
and local-first context mining.
Aggregate findings into a PASS, FAIL, or NEEDS-CONTEXT verdict, and cite the
evidence used for every lane.
Manual-QA channels must leave artifacts, cleanup receipt paths, and bounded
session teardown proof. Respect the publish boundary: reviewing release
readiness is allowed, but npm publish, remote marketplace registration, and
other remote mutation still need explicit user approval.

Lane routing:

- goal and constraint verification: use `oracle-verifier` with `review-work`
  and `rules`.
- hands-on QA execution: use `qa-runner` with `start-work` and `review-work`.
- code quality review: use `quality-reviewer` with `review-work` and
  `programming`.
- security review: use `quality-reviewer` with `review-work` and
  `programming`.
- local-first context mining: use `librarian-researcher` with `rules`.

Before launching broad review work, check whether native goal tools are
available and bind the review to the active goal. If goal tools are unavailable,
keep the local evidence ledger authoritative. For large independent lanes, use
Dynamic workflow when Claude Code exposes it, and use `claude --worktree` only
when isolated review edits or reproduction steps need a separate checkout.
Use current docs/test reads before trusting stale local state or continuation
notes.
