review

/mz:review

Perform on-demand two-stage code review (spec compliance + code quality) independently of the /mz:go pipeline. Users can trigger this manually at any time, regardless of the quality.review config setting. Spawns a reviewer subagent via the Task tool that checks changes against plan specs and code quality standards.

Reference @skills/init/design-system.md for visual output formatting. Reference @agents/mz-reviewer.md for the review agent definition.

Step 1: Display Banner

Output the stage banner:

+===============================================+
|  MEGAZORD > REVIEW                            |
+===============================================+

Step 2: Parse Arguments and Determine Scope

Parse the user's message (text after /mz:review) for the review target:

• /mz:review (no args) -- review the most recent commit's changes
• /mz:review --plan {phase}-{plan} -- review all changes from a specific plan (diff from before plan started to after plan completed)
• /mz:review --files path/to/file.ts path/to/other.ts -- review specific files (diff of uncommitted changes, or latest commit affecting those files)
• /mz:review --last N -- review the last N commits

Determine the diff to review based on the scope:

No args (default):

git diff HEAD~1 HEAD

--plan {phase}-{plan}: Compute diff range from plan's first to last commit. Read the plan's SUMMARY.md for commit hashes:

1. Read SUMMARY.md in the phase directory for the specified plan.
2. Extract the first and last commit hashes from the Task Commits section.
3. Compute: git diff {first_commit}~1 {last_commit}

If SUMMARY.md not found, report error: plan has not been executed yet.

--files {file1} {file2} ...: Check for uncommitted changes first:

git diff HEAD -- {files}

If no uncommitted changes, find latest commit affecting those files:

git log -1 --format=%H -- {files}

Then diff: git diff {hash}~1 {hash} -- {files}

--last N:

git diff HEAD~{N} HEAD