mcpField
R
review-docs

review-docs

github.com/reactjsTesting & quality11.8k78 installsUpdated 4d ago
Repository

About review-docs

review-docs is a documentation review skill that directs agents to check files using the relevant writing and style skills. It specifies parallel review tasks by content type and asks for a consolidated checklist with line numbers.

Key features

  1. 01Parallel review task checklist
  2. 02Checks selected by documentation type
  3. 03Voice and component review prompts
  4. 04Sandpack review for applicable files
  5. 05Consolidated findings with line numbers

Use cases

  1. 01Reviewing modified documentation files
  2. 02Checking learn, reference, or blog content
  3. 03Auditing documentation voice and components
  4. 04Collecting review issues before planning fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/reactjs/react.dev --skill review-docs

After installing, type/review-docsin Claude Code to confirm it loaded.

Details

From the project README

CRITICAL: do not load these skills yourself.

Run these tasks in parallel for the given file(s). Each agent checks different aspects—not all apply to every file:

  • Ask docs-reviewer agent to review {files} with docs-writer-learn (only for files in src/content/learn/).
  • Ask docs-reviewer agent to review {files} with docs-writer-reference (only for files in src/content/reference/).
  • Ask docs-reviewer agent to review {files} with docs-writer-blog (only for files in src/content/blog/).
  • Ask docs-reviewer agent to review {files} with docs-voice (all documentation files).
  • Ask docs-reviewer agent to review {files} with docs-components (all documentation files).
  • Ask docs-reviewer agent to review {files} with docs-sandpack (files containing Sandpack examples).

If no file is specified, check git status for modified MDX files in src/content/.

The docs-reviewer will return a checklist of the issues it found. Respond with the full checklist and line numbers from all agents, and prompt the user to create a plan to fix these issues.

Comments

Markdown supported