revise-doc

Applies review findings from rNN- review files to a document during validate-loop iteration.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill revise-doc-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revise-doc
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/revise-doc
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill revise-doc-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After reviewers produce findings on a document, someone must manually walk each finding, decide which edits to apply, and reconcile conflicting suggestions. This Skill automates that act-pass: it reads rNN-{focus}.md review files, filters findings by severity, applies concrete edits to the artifact, and surfaces contradictions instead of silently picking a winner. ## Core Features & Use Cases - Severity-filtered editing: Always applies Blockers and Majors, applies Minors with concrete suggestions, and defers Nits unless explicitly opted in via includeNits. - Contradiction handling: When two reviewers prescribe incompatible fixes for the same location, it surfaces both to the captain rather than choosing one. - Structured reporting: Prints a summary of applied, deferred, and contradicted findings with counts; never writes files, commits, or spawns subagents. - Use Case: During a validate-loop iteration, triage routes an act cluster of findings from three review files to this Skill, which groups them by document location, applies the unambiguous fixes one at a time, and reports two contradictions for the captain to resolve. ## Quick Start Apply the findings from r01-architecture.md and r02-accuracy.md to the plan document at docs/plan.md and report which edits were applied or deferred.

Frequently Asked Questions about revise-doc

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

FAQPage Schema
How do I apply code review findings to a document automatically?▼

Provide the artifact path and one or more rNN-{focus}.md review files containing findings grouped by severity. The Skill walks each finding, applies concrete edits via Edit calls, and reports applied versus deferred items.

How to handle contradicting reviewer suggestions on the same text?▼

When two findings prescribe incompatible fixes for the same location, the Skill refuses to pick a winner. It marks the finding as a contradiction, surfaces both suggested fixes to the captain in the report, and continues with remaining findings.

Can I pass findings directly instead of review files?▼

Yes, use the inlineFindings input when the lifecycle skill has already extracted clusters from triage output. Either reviewFilePaths or inlineFindings must be supplied, but not both are required.

Does the revise-doc skill apply nit-level findings?▼

Nits are skipped by default and recorded as deferred with reason nit-no-opt-in. Set includeNits to true to apply them; per decision d11, nits normally route to defer rather than act.

What are the limitations of automated review-finding application?▼

It only edits sections referenced by findings, never invents new findings, and never commits changes. Vague findings without concrete fixes are marked needs-process and surfaced rather than guessed at.