plugins/gsd/skills/code-review/SKILL.md
Review source files changed during a phase for bugs, security issues, and code quality problems
npx skillsauth add davepoon/buildwithclaude gsd:code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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)Output: {padded_phase}-REVIEW.md in phase directory + inline summary of findings </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/code-review.md </execution_context>
<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-sdk query init.phase-op and delegated to agent via <files_to_read> blocks.
</context>
Execute the code-review workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/code-review.md end-to-end.
The workflow (not this command) enforces these gates:
development
Show drill-me learning progress — topics studied, cards due for review, weakest concepts, and what to study next. Use when the user asks what's due, how their learning is going, or for their drill-me status.
development
Teach the user a topic as an adaptive tutor — retrieval practice, spaced repetition with decay, and persistent memory in ~/.drill-me/. Use when the user wants to learn or be drilled on something, says "drill me on X", "teach me X", or wants to study a topic, a codebase, or a document.
development
Turn any codebase into evidence-grounded Markdown docs plus a machine-readable index.json. Every claim cites its source; never invents deployment steps.
tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.