gsd-code-review-fix

Auto-fix code review issues from REVIEW.md and generate REVIEW-FIX.md.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-code-review-fix-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-code-review-fix
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-code-review-fix
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-code-review-fix-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-fix issues found by code review in REVIEW.md for a given phase, spawning a fixer agent to apply fixes and producing a phase-specific REVIEW-FIX.md summary.

Core Features & Use Cases

  • Auto-fix issues found in code-review REVIEW.md by applying fixes atomically
  • Commit each fix separately to preserve clear history
  • Generate a concise REVIEW-FIX.md summary for traceability

Quick Start

Provide the phase number and optional flags to begin auto-fixing your code-review for that phase and emit a REVIEW-FIX.md summary.

Frequently Asked Questions about gsd-code-review-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code-review fixes from a REVIEW.md file?

Automate code-review fixes by spawning a fixer agent that reads REVIEW.md, applies atomic fixes for a given phase, commits each change separately, and generates a REVIEW-FIX.md summary for traceability.

Can I automatically fix all code-review issues across multiple phases at once?

Yes, you can automatically fix issues across phases using the --all option. The --auto option further enables iterative fixing, applying up to three automated fix iterations per phase.

How does atomic code fixing preserve my git workflow history?

Atomic code fixing preserves git workflow history by applying each fix as a separate commit. This ensures a clear, traceable commit log for every change made during the code-review resolution process.

What is a REVIEW-FIX.md summary and why do I need it after code review?

A REVIEW-FIX.md summary is a concise report generated after fixing code-review issues. It documents what fixes were applied, providing traceability and a clear record of resolved review problems.

How do I start an automated code review fixer for a specific development phase?

Start the automated code review fixer by providing the phase number and optional flags like --all or --auto. The tool then processes the REVIEW.md for that phase, applies fixes, and outputs the summary.