gsd-code-review

name	gsd-code-review
description	Review source files changed during a phase for bugs, security issues, and code quality problems

<augment_skill_adapter>

A. Skill Invocation

• This skill is invoked when the user mentions gsd-code-review or describes a task matching this skill.
• Treat all user text after the skill mention as {{GSD_ARGS}}.
• If no arguments are present, treat {{GSD_ARGS}} as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

• Present options as a numbered list in your response text
• Ask the user to reply with their choice
• For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Augment tools when executing GSD workflows:

• launch-process for running commands (terminal operations)
• str-replace-editor for editing existing files
• view for reading files and listing directories
• save-file for creating new files
• grep for searching code (or use MCP servers for advanced search)
• web-search, web-fetch for web queries
• add_tasks, view_tasklist, update_tasks for task management

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use the built-in subagent spawning capability
• Define agent prompts in .augment/agents/ directory </augment_skill_adapter>

Review source files changed during a phase for bugs, security vulnerabilities, 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:

• Phase number (required) — which phase's changes to review (e.g., "2" or "02")
• --depth=quick|standard|deep (optional) — review depth level, overrides workflow.code_review_depth config
  • quick: Pattern-matching only (~2 min)
  • standard: Per-file analysis with language-specific checks (~5-15 min, default)
  • deep: Cross-file analysis including import graphs and call chains (~15-30 min)
• --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 iterations

Output: {padded_phase}-REVIEW.md in phase directory + inline summary of findings

<execution_context> @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/code-review.md </execution_context>

Phase: {{GSD_ARGS}} (first positional argument is phase number)

Optional flags parsed from {{GSD_ARGS}}:

• --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 (.augment/rules/, 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.

This command is a thin dispatch layer. It parses arguments and delegates to the workflow.

Execute the code-review workflow from @/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/code-review.md end-to-end.

The workflow (not this command) enforces these gates:

• Phase validation (before config gate)
• Config gate check (workflow.code_review)
• File scoping (--files override > SUMMARY.md > git diff fallback)
• Empty scope check (skip if no files)
• Agent spawning (gsd-code-reviewer)
• Result presentation (inline summary + next steps)