review-fix

Runs configurable review-and-fix rounds on a change until reviewers report clean.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/wkentaro/skills --skill review-fix-wkentaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-fix
Source: https://github.com/wkentaro/skills/tree/main/skills/in-progress/review-fix
Command: npx skills add https://github.com/wkentaro/skills --skill review-fix-wkentaro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a change, verifying each finding, repairing real defects, and re-reviewing until clean is a repetitive multi-round loop that is easy to do inconsistently. This Skill orchestrates that entire cycle with a defined review policy, claim tracking, and verification gates, while leaving all repairs uncommitted. ## Core Features & Use Cases - Configurable Review Policy: Run the built-in Default Review Policy (code-review, brooks-review, ask-exemplar, zero-tech-debt, writing-code), name specific review skills, or supply a free-form brief that becomes an ad-hoc review request. - Verified Findings Only: Every reviewer claim is independently verified against the source, a Scope Contract, or direct checks before any repair; speculative hardening and scope expansion are rejected and recorded. - Adaptive Rounds with Gates: Repairs pass Synthesis and Repair Gates, then trigger Full or Delta re-review rounds until the change is clean, with remote CI classified as evidence, stale, or infrastructure failure. - Use Case: Before merging a pull request, run /review-fix #123 to have report-only reviewers inspect the diff, fix verified defects, re-review the repair, and receive a clean outcome with a downstream handoff summary. ## Quick Start Ask the AI to run /review-fix on the current branch or a specific PR number, optionally adding a free-form review brief such as a security or maintainability focus.

Frequently Asked Questions about review-fix

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

FAQPage Schema
How do I run automated review-and-fix rounds on a pull request?▼

Run /review-fix followed by the PR number, such as /review-fix #123. The skill resolves the PR into an editable checkout, dispatches report-only reviewers, repairs verified findings, and re-reviews until the change is clean.

What happens when I run a code review without specifying a brief?▼

With no brief, the Default Review Policy applies: five review requests covering code-review, brooks-review, ask-exemplar, zero-tech-debt in analysis-only mode, and writing-code in audit mode. Each gets a fresh report-only reviewer.

Does the review-fix workflow commit or push the repairs it makes?▼

No. All repairs are left uncommitted in the working tree. The skill never commits, rebases, comments on a forge, or pushes; the caller retains full control of repository history and publication.

How are reviewer findings verified before any code is changed?▼

Each claim is independently checked against the source, a Scope Contract, repository standards, or a direct observable check. Only verified findings receive repairs; disproved or unverifiable claims are recorded as rejected or unverified.

Can I use custom review criteria instead of the default review skills?▼

Yes. A free-form brief creates one ad-hoc reviewer using the brief as its criteria, and explicitly named review skills replace the Default Review Policy. Ambiguous matches trigger a structured selection before any reviewer starts.

What happens if a reviewer fails or times out during a review round?▼

The run ends with an incomplete outcome. No orchestrator edits or partial repairs are applied, and the target, repository history, and forge state remain unchanged.