gsd-code-review-fix

Apply code review fixes from REVIEW.md and generate a REVIEW-FIX.md summary.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-code-review-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-code-review-fix
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-code-review-fix
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-code-review-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the remediation of issues raised during code reviews by reading a REVIEW.md file for a specified phase, spawning a fixer agent, applying fixes atomically, and producing a REVIEW-FIX.md summary.

Core Features & Use Cases

  • Auto-fix issues found in REVIEW.md by spawning a dedicated fixer agent.
  • Commit each fix atomically and generate a concise REVIEW-FIX.md summary.
  • Supports phase-based operation with optional --all and --auto flags to control scope and iteration.

Quick Start

Invoke the skill with the phase number and optional flags to fix the specified REVIEW.md and produce a phase-level 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 fixing code review issues in a markdown file?▼

To automate fixing code review issues, this skill reads a REVIEW.md file, spawns a fixer agent to apply the corrections, and outputs a REVIEW-FIX.md summary in the phase directory.

Can I automatically re-run the code review fix cycle until all issues are resolved?▼

Yes, you can automatically re-run the code review fix cycle up to three iterations by invoking the skill with the --auto flag to ensure issues are resolved.

How do I apply code review fixes across all project phases at once?▼

To apply code review fixes across all phases at once, run the skill with the --all flag, which processes the REVIEW.md files for every phase and generates corresponding fix summaries.

What is the best way to track applied fixes after automating code review remediation?▼

The best way to track applied fixes is through the generated REVIEW-FIX.md file, which provides an inline summary of all corrections applied atomically by the fixer agent.

Does the code review fixer require any external dependencies to run?▼

No, the code review fixer requires no external dependencies to run; it only needs a REVIEW.md file present in the specified phase directory to begin processing.

When should I use phase-based code review remediation instead of fixing all issues globally?▼

Use phase-based code review remediation when working through incremental project stages, allowing targeted fixes per phase directory rather than applying broad changes globally.