code-fixer

Apply targeted fixes from AI_REVIEW.md and log changes to AI_CHANGES.md.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill code-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-fixer
Source: https://github.com/hoonzinope/skills/tree/main/code-fixer
Command: npx skills add https://github.com/hoonzinope/skills --skill code-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Read .documents/review/AI_REVIEW.md, implement fixes, and log changes into .documents/review/AI_CHANGES.md.

Core Features & Use Cases

  • Parse the latest review round in AI_REVIEW.md and identify actionable fixes.
  • Apply minimal, targeted changes (blocker-first; small batch) and generate a changelog entry.
  • Append a structured round summary to .documents/review/AI_CHANGES.md with round, summary, files changed, commands run, and follow-ups.

Quick Start

Read the latest AI_REVIEW.md, implement a small batch of fixes, and append a dated round to AI_CHANGES.md.

Frequently Asked Questions about code-fixer

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

FAQPage Schema
How do I automate applying code review fixes and logging changes to a changelog?

Automating code review fixes involves parsing the latest AI_REVIEW.md, applying blocker-first small-batch targeted changes, and appending a structured commit-like summary to AI_CHANGES.md for traceable progress.

What is the best way to track AI-assisted code review fixes in a structured changelog?

Tracking AI-assisted code review fixes is done by appending a dated round summary containing the round number, summary, files changed, commands run, and follow-ups to the AI_CHANGES.md file.

How do I apply small-batch fixes from an AI review file without modifying files outside the review scope?

Applying small-batch fixes from an AI review file uses guardrails that restrict write operations strictly to the .documents/ directory, updating the review status or leaving it untouched as appropriate.

Can I use an AI assistant to parse AI_REVIEW.md and update the review status automatically?

Yes, an AI assistant can parse the latest actionable review round in AI_REVIEW.md, apply minimal targeted fixes, and automatically update or leave the review status untouched within the .documents/ directory.

What limitations exist when using an automated AI assistant for code review fixes?

Limitations include restricting the scope to blocker-first small-batch fixes and enforcing write guardrails that confine all changes and changelog updates exclusively to the .documents/ directory.

Why does my code review changelog need a commit-like summary appended to AI_CHANGES.md?

A commit-like summary in AI_CHANGES.md provides traceable progress by documenting the round, summary, files changed, commands run, and follow-ups for each batch of applied review fixes.