docs-reviewer

Audit READMEs, API docs, and code comments against repository code.

9|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/mattdurham/bob --skill docs-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-reviewer
Source: https://github.com/mattdurham/bob/tree/main/agents/docs-reviewer
Command: npx skills add https://github.com/mattdurham/bob --skill docs-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure documentation accuracy and completeness by auditing project docs against the actual codebase, identifying mismatches and gaps that mislead users.

Core Features & Use Cases

  • Review README, API docs, and code comments for accuracy.
  • Validate that code examples match implementation and compile when tested.
  • Generate a Documentation Review Report at bots/review-docs.md to document findings and recommended fixes.

Quick Start

Spawn the docs-reviewer as part of a workflow to automatically audit your repository's documentation and produce a findings report.

Frequently Asked Questions about docs-reviewer

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

FAQPage Schema
How do I audit README files against my codebase to ensure documentation accuracy?

To audit README accuracy, spawn the docs-reviewer to review your project documentation against the actual codebase, verifying that examples match implementation and generating a findings report at bots/review-docs.md for remediation.

What is the best way to validate API documentation and code comments across a repository?

Validating API documentation and code comments involves auditing project docs against the codebase to identify mismatches and gaps. This process produces a formal Documentation Review Report ensuring accuracy and completeness for users.

Can I automatically generate a documentation review report for my repository?

Yes, you can automatically generate a documentation review report by spawning the docs-reviewer as part of a workflow. It audits your repository and outputs findings to bots/review-docs.md with recommended fixes.

Does the documentation review process check if code examples compile and match the implementation?

Yes, the documentation review process validates that code examples match implementation and compile when tested. It audits READMEs, API docs, and in-code comments to ensure accuracy and completeness.

Why does my API documentation have mismatches with the actual code implementation?

API documentation mismatches occur when docs are not audited against the codebase. Reviewing API docs and code comments identifies gaps and inaccuracies, producing a formal findings report to guide remediation.

When do I need a formal documentation review report for my project?

You need a formal documentation review report when ensuring documentation accuracy and completeness across a repository. It audits READMEs, API docs, and code comments against code to identify mismatches that mislead users.