gsd:code-review

A command that reviews source files changed in a development phase for bugs, security problems, and code-quality issues.

In plain words
What is it for?
Use it to review a phase's files at quick, standard, or deep detail, optionally naming files directly or applying and rechecking proposed fixes.
Why use it?
It produces a severity-labeled review so problems can be found before the phase is considered complete, with optional automatic fixes and another review.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/mrboups/xbrain/code-review
Clone the repo
git clone --depth 1 https://github.com/mrboups/xbrain

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 684 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00684
Opus 5 $0.00012 $0.00342
Sonnet 5 $0.00005 $0.00137
Haiku 4.5 $0.00002 $0.00068

Measured yesterday against content hash 429ce17fddc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd:code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

89% identical to gsd:code-review — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/gsd/code-review.md · 59 lines

What it actually says

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> @D:/VSC/xbrain/.claude/get-shit-done/workflows/code-review.md </execution_context>

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.

Execute the code-review workflow from @D:/VSC/xbrain/.claude/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)
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 59 lines · 23 tokens per session scan A 429ce17fddc1

Subscribe to this mod's changes

gsd:code-review is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 18d ago), licensed MIT. It adds 23 tokens to every session and 684 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gsd:code-review, differing in 11 lines, and is treated as a copy.