coco-research/gsd-code-review-fix
Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
npx skills add https://github.com/coco-research/coco --skill gsd-code-review-fix
<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:
--all (optional) — include Info findings in fix scope (default: Critical + Warning only)--auto (optional) — enable fix + re-review iteration loop, capped at 3 iterationsOutput: {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:
</process>
Take coco-research/gsd-code-review-fix from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.