Skills

Gsd Code Review Fix

Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning...

Install

npx skills add coco-research/coco --skill gsd-code-review-fix -g -a claude-code -y
Repository
coco-research/coco797
Category
AI and agents
Updated
3d ago
License
See repository
Context cost
Lightabout 456 tokens
Runs scripts
No, instructions only

What it does

Use after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).

<objective> Auto-fix issues found by code review. Reads REVIEW.md from the specified phase, spawns gsd-code-fixer agent to apply fixes, and produces REVIEW-FIX.md summary.

Arguments:

  • Phase number (required), which phase's REVIEW.md to fix (e.g., "2" or "02")
  • --all (optional), include Info findings in fix scope (default: Critical + Warning only)
  • --auto (optional), enable fix + re-review iteration loop, capped at 3 iterations

Output: {padded_phase}-REVIEW-FIX.md in phase directory + inline summary of fixes applied </objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/code-review-fix.md </execution_context>

<context> Phase: $ARGUMENTS (first positional argument is phase number)

Optional flags parsed from $ARGUMENTS:

  • --all, Include Info findings in fix scope. Default behavior fixes Critical + Warning only.
  • --auto, Enable fix + re-review iteration loop. After applying fixes, re-run code-review at same depth. If new issues found, iterate. Cap at 3 iterations total. Without this flag, single fix pass only.

Context files (CLAUDE.md, REVIEW.md, phase state) are resolved inside the workflow via gsd-tools init phase-op and delegated to agent via config blocks. </context>

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

Execute the code-review-fix workflow from @$HOME/.claude/get-shit-done/workflows/code-review-fix.md end-to-end.

The workflow (not this command) enforces these gates:

  • Phase validation (before config gate)
  • Config gate check (workflow.code_review)
  • REVIEW.md existence check (error if missing)
  • REVIEW.md status check (skip if clean/skipped)
  • Agent spawning (gsd-code-fixer)
  • Iteration loop (if --auto, capped at 3 iterations)
  • Result presentation (inline summary + next steps) </process>

More in AI and agents