agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-code-review/SKILL.md

gsd-code-review

Skill1 starsChanged 31 days agoMITView on GitHub

Review source files changed during a phase for bugs, security issues, and code quality problems

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md
<objective> 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 </objective>

<execution_context> @$HOME/.claude/get-shit-done/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>

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

Execute 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)</process>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free