Review source files changed during a phase for bugs, security issues, and code quality problems
65%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./pi/package-skills/gsd-code-review/SKILL.mdInvoke this Pi skill with /skill:gsd-code-review.
Pi dispatch (fail closed). Pi has no built-in subagent API; GSD provides the gsd_dispatch tool. Where a workflow step dispatches a named gsd-* role, call gsd_dispatch with role (the installed role name) and task (the full task text). A workflow that still writes the step as an Agent(...) call means the same: its subagent_type is the role and its prompt is the task. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If gsd_dispatch reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.
Pi includes. Pi does not expand @path references in a skill. Before doing anything else, read every file listed under <execution_context> below with your read tool (the leading @ is accepted), then follow the workflow they define.
(the text typed after the skill name)
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
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 iterationsgsd_run review-lane flags (the canonical reviewer-lane roster; e.g. --codex, --agy) requests that lane independently review the same already-resolved scope alongside the internal gsd-code-reviewer agent. Its findings are corroborating evidence only — gsd-code-reviewer alone verifies each claim against the actual source and writes REVIEW.md; there is exactly one REVIEW.md schema. No reviewer-lane flag (the default) reviews with only the internal agent, byte-for-byte unchanged from before #4209.Output: {padded_phase}-REVIEW.md in phase directory + inline summary of findings
<execution_context> @GSD_PI_ENGINE_ROOT/gsd-core/workflows/code-review.md </execution_context>
Phase: the `` block (first positional argument is phase number)Optional flags parsed from the <arguments> block:
--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.
Reviewer lanes run without a phase (gsd_run is defined by the runtime-launcher preamble inside workflow fences; in a plain shell call node <install>/gsd-core/bin/gsd-tools.cjs instead): pipe canonical repo-relative file paths (one per line) to stdin of
gsd_run review-lane dispatch-step --repo-root <root> --depth <quick|standard|deep> --base-sha <sha> --run-dir "$(mktemp -d)" --cap-id code-review --point execute:post --explicit <slugs> --raw.
review-lane flags are space-separated (--depth quick), never --flag=value. --explicit (omitted, nothing dispatches yet the call exits ok), --depth, --base-sha (lane reviews changes relative to it; commit them first) and stdin paths are required; --run-dir should be a fresh temp dir (default . writes the prompt file into the current directory); read each lane's output path (results[].reviewPath) from the JSON before removing it. --cap-id/--point select the code-review capability, which must be enabled (workflow.code_review) and active at --point — execute:post, or execute:wave:post when workflow.code_review_point selects it; otherwise nothing dispatches.
--explicit takes comma-separated canonical slugs, no spaces (codex,antigravity), not flag aliases (antigravity, not agy); slugs: first column of gsd_run review-lane sections (review-lane flags lists flags/aliases).
Each lane declares its own model key, which is not always its slug (antigravity's is review.models.agy); see the review.models.* table in docs/CONFIGURATION.md. Unset = lane default model.
Execute end-to-end.
The workflow (not this command) enforces these gates:
open-gsd/gsd-core
99bbbac
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.