Review source files changed during a phase for bugs, security issues, and code quality problems
Spawns the gsd-code-reviewer agent to analyze code at the specified depth level. Produces REVIEW.md artifact in the phase directory with severity-classified findings.
Arguments:
--depth=quick|standard|deep (optional) — review depth level, overrides workflow.code_review_depth config
--files file1,file2,... (optional) — explicit comma-separated file list, skips SUMMARY/git scoping (highest precedence for scoping)--fix (optional) — after review completes (or if REVIEW.md already exists), auto-apply fixes found. Spawns gsd-code-fixer agent. Accepts sub-flags:
--all — include Info findings in fix scope (default: Critical + Warning only)--auto — enable fix + re-review iteration loop, capped at 3 iterationsOutput: {padded_phase}-REVIEW.md in phase directory + inline summary of findings
<execution_context> @~/.claude/gsd-core/workflows/code-review.md </execution_context>
Phase: $ARGUMENTS (first positional argument is phase number)Optional flags parsed from $ARGUMENTS:
--depth=VALUE — Depth override (quick|standard|deep). If provided, overrides workflow.code_review_depth config.--files=file1,file2,... — Explicit file list override. Has highest precedence for file scoping per D-08. When provided, workflow skips SUMMARY.md extraction and git diff fallback entirely.Context files (CLAUDE.md, SUMMARY.md, phase state) are resolved inside the workflow via gsd-tools query init.phase-op and delegated to agent via <required_reading> blocks.
Execute end-to-end.
The workflow (not this command) enforces these gates:
abf3cf7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.