review-doc

Reviews one markdown artifact through a single focus and writes a structured rNN-{focus}.md findings file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Document review in multi-agent workflows often produces inconsistent, overlapping, or unscoped feedback. This Skill enforces a single-focus review discipline: one reviewer, one persona, one artifact, one structured findings file, so orchestrators like validate-doc can fan out parallel reviews and triage-feedback can parse uniform output. ## Core Features & Use Cases - Focus-driven review: Resolves a focus brief (accuracy, architecture, clarity, comprehensiveness, depth, dx, integration, scope) that defines the persona, signals to flag, verification recipe, and severity calibration. - Persona adoption: Borrows the cognitive profile of a named persona agent (architect, qa, doc-writer, reviewer, researcher, dx) while keeping read-only tools. - Standardized output: Writes an rNN-{focus}.md file with fixed Blockers/Majors/Minors/Nits sections so downstream triage parses one shape. - Use Case: An orchestrator validating a plan chapter dispatches this Skill with focus=accuracy; it verifies every external claim against primary sources at the pinned version and writes r03-accuracy.md next to the chapter. ## Quick Start Dispatch this skill with a focus name, the artifact path, the target rNN filename, and an iteration number to produce a single-focus review file alongside the artifact.

Frequently Asked Questions about review-doc

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

FAQPage Schema
How do I run a single-focus document review with this skill?▼

Provide four inputs: the focus name, the absolute artifact path, the exact rNN-{focus}.md target filename, and the iteration number. The skill resolves the focus brief, adopts the named persona, reviews the artifact, and writes the findings file.

What review focuses are available for document review?▼

Eight baseline focuses ship with the skill: accuracy, architecture, clarity, comprehensiveness, depth, dx, integration, and scope. Contextual focuses like security, performance, and compatibility are supported but require authoring a focus brief first.

Can the review-doc skill edit the artifact it reviews?▼

No. The skill runs with read-only tools (Read, Glob, Grep, WebFetch, WebSearch) and its only write is the rNN-{focus}.md findings file. It cannot modify the artifact, other reviews, or spawn subagents.

What output format does the review file use?▼

Every review file uses one fixed template: a header with artifact, focus, and persona, a summary, then four severity sections (Blockers, Majors, Minors, Nits) always present in order, with empty sections written as (none) so triage-feedback parses one shape.

What happens if findings fall outside the assigned focus?▼

Out-of-scope findings are not filed. Each focus brief includes a binding what-not-to-flag list, and cross-reviewer synthesis is delegated to triage-feedback rather than the individual reviewer.