# Review Docs

> Use when reviewing React documentation for structure, components, and style compliance

Use when reviewing React documentation for structure, components, and style compliance

- Page: https://ss33.ai/skills/reactjs/review-docs-4398544590
- Publisher: reactjs
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [Developer docs & tooling](https://ss33.ai/skills/category/software-development-t44z8z/developer-docs-and-tooling-nich6w)
- License: CC-BY-4.0
- Source: https://github.com/reactjs/react.dev/blob/046f17d04295ba047bb5739026b4ac3110f17028/.claude/skills/review-docs/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/reactjs/review-docs-4398544590

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.