documentation-lens

Assess documentation completeness and accuracy across a codebase.

30|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/atomicinnovation/accelerator --skill documentation-lens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-lens
Source: https://github.com/atomicinnovation/accelerator/tree/main/skills/review/lenses/documentation-lens
Command: npx skills add https://github.com/atomicinnovation/accelerator --skill documentation-lens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve the usefulness of project documentation by evaluating completeness, accuracy, audience fit, and discoverability against the project's existing documentation norms so readers can succeed without asking the author for help.

Core Features & Use Cases

  • API and Interface Coverage: Check that public APIs, function signatures, and data models include purpose, parameters, return values, error conditions, and working examples where appropriate.
  • Developer-Facing Guidance: Assess README, getting-started guides, architecture notes, changelogs, and migration guidance for accuracy and sufficiency during onboarding or pre-implementation reviews.
  • Inline and Consistency Checks: Identify outdated or misleading comments, missing rationale for complex logic, inconsistent claims between code and docs, and provide confidence ratings for each finding.
  • Use Case: Use during plan review to surface documentation gaps that would block a developer from implementing or maintaining the planned changes.

Quick Start

Review the repository documentation for missing or incorrect sections, produce a prioritized list of issues with confidence ratings, and suggest actionable improvements.

Frequently Asked Questions about documentation-lens

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

FAQPage Schema
How do I check my codebase documentation for missing API parameters and examples?

To check codebase documentation completeness, evaluate public APIs and data models to ensure they include purpose, parameters, return values, error conditions, and working examples. The review identifies missing API parameter descriptions and provides confidence ratings for each finding.

What is the best way to review a README and getting-started guides for developer onboarding?

Reviewing README and getting-started guides for onboarding involves assessing accuracy and sufficiency against project norms. This ensures developer-facing guidance enables readers to succeed without asking the author for help by identifying inconsistent claims or missing rationale.

Can I detect outdated inline comments and inconsistent claims between code and docs?

Yes, you can detect outdated inline comments and inconsistent claims by performing consistency checks across the codebase. The process identifies misleading comments, missing rationale for complex logic, and discrepancies between code and docs with confidence ratings.

Does this documentation review work for pull request evaluations and plan reviews?

Yes, documentation review works for pull request evaluations and plan reviews by surfacing documentation gaps that would block a developer from implementing or maintaining planned changes. It evaluates completeness, accuracy, audience fit, and discoverability during these checks.

How do I get a prioritized list of documentation issues in my repository?

To get a prioritized list of documentation issues, review the repository documentation for missing or incorrect sections. This produces a prioritized list of issues with confidence ratings and suggests actionable improvements to enhance overall doc quality.