Documentation review

Reviews documentation for factual accuracy

153 stars

Best use case

Documentation review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Reviews documentation for factual accuracy

Teams using Documentation review should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/documentation-review/SKILL.md --create-dirs "https://raw.githubusercontent.com/Microck/ordinary-claude-skills/main/skills_all/documentation-review/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/documentation-review/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Documentation review Compares

Feature / AgentDocumentation reviewStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Reviews documentation for factual accuracy

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Generating Commit Messages

## Instructions

1. Read the documentation you are instructed to review
2. Make sure that all claims about how toolhive works are accurate
3. Make sure that all examples are based in how toolhive really works, check for formatting, typos and overall accuracy
4. Make sure that all links point to existing files and the content of the links matches what it should

## Fact-checking claims in the documentation

See [CHECKING.md](CHECKING.md) on instructions on how to check claims in the docs.

You have some examples on how to fact-check in [EXAMPLES.md](EXAMPLES.md)

## Your report

- Do not suggest inline changes
- Present findings and put each into a todo list. The user will then go through them and review manually

Related Skills

woocommerce-code-review

153
from Microck/ordinary-claude-skills

Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.

typescript-review

153
from Microck/ordinary-claude-skills

Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.

reviewing-pr

153
from Microck/ordinary-claude-skills

Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings

Reviewing Code

153
from Microck/ordinary-claude-skills

Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.

reviewing-changes

153
from Microck/ordinary-claude-skills

Android-specific code review workflow additions for Bitwarden Android. Provides change type refinements, checklist loading, and reference material organization. Complements bitwarden-code-reviewer agent's base review standards.

github-code-review

153
from Microck/ordinary-claude-skills

Comprehensive GitHub code review with AI-powered swarm coordination

docs-review

153
from Microck/ordinary-claude-skills

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

code-review-excellence

153
from Microck/ordinary-claude-skills

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

clojure-review

153
from Microck/ordinary-claude-skills

Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing Clojure/ClojureScript code.

peer-review

153
from Microck/ordinary-claude-skills

Systematic peer review toolkit. Evaluate methodology, statistics, design, reproducibility, ethics, figure integrity, reporting standards, for manuscript and grant review across disciplines.

literature-review

153
from Microck/ordinary-claude-skills

Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).

zapier-workflows

153
from Microck/ordinary-claude-skills

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.