review-fix

Parse review findings and apply wave-ordered fixes with atomic commits.

18|2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/jhd3197/CachiBot --skill review-fix-jhd3197
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-fix
Source: https://github.com/jhd3197/CachiBot/tree/main/.claude/skills/review-fix
Command: npx skills add https://github.com/jhd3197/CachiBot --skill review-fix-jhd3197

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many repositories accumulate review findings that are documented but never consistently applied, leaving technical debt and broken linters behind. This Skill automates reading the newest review, synthesizing prioritized fix actions, and applying minimal, auditable changes so maintainers can close review gaps quickly and safely.

Core Features & Use Cases

  • Discover & parse: Finds the most recent .reviews/*-review.md and extracts structured findings with severity, file, line, and reviewer metadata.
  • Parallel planning agents: Spawns scoped planners (backend, frontend, data, tests) that group related findings, rank by severity, and produce a wave-ordered review-plan.
  • Wave-based execution: Applies fixes wave-by-wave with minimal edits, runs ruff/npm linters, stages changes, and creates one atomic commit per wave while producing a review-execution log.
  • Auditable outputs: Generates .reviews/YYYY-MM-DD-review-plan.md and .reviews/YYYY-MM-DD-review-execution.md documenting decisions, commits, and skipped items.
  • Use case: A maintainer runs this to turn a recent architectural/code-quality review into prioritized, tested fixes and atomic commits without manual patching.

Quick Start

Run the review-fix skill to read the latest review file, generate a prioritized plan, and apply fixes with atomic commits.

Frequently Asked Questions about review-fix

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

FAQPage Schema
How do I automate applying fixes from a code review file?

You can automate applying code review fixes by parsing findings from .reviews/*-review.md files, generating wave-ordered plans, and executing minimal edits with linters and atomic commits. This Skill handles backend, frontend, data, and test remediation automatically.

What is the best way to turn code review findings into atomic commits?

Turning code review findings into atomic commits requires wave-based execution that groups related fixes by severity and file scope. This Skill stages changes per wave, creating one atomic commit per wave while producing execution logs.

Does this code review automation tool work with ruff and npm linters?

Yes, this code review automation works with ruff and npm linters by running them during wave-based execution. It applies minimal edits to resolve findings and validates changes using these linters before staging and committing.

How do I prioritize backend, frontend, and data fixes from a repository review?

You can prioritize backend, frontend, and data fixes by spawning parallel planning agents that group related findings and rank them by severity. This generates a wave-ordered review-plan ensuring high-severity issues are addressed first.

Can I generate an execution log for code review remediation?

Yes, you can generate an execution log for code review remediation. The Skill outputs .reviews/YYYY-MM-DD-review-execution.md files documenting decisions, commits, and skipped items alongside a corresponding review-plan file for full auditability.

What file format does this tool require for code review findings?

This tool requires code review findings stored as markdown files matching the .reviews/*-review.md format. It parses these files to extract structured findings including severity, file, line, and reviewer metadata for automated remediation.