devflow:docs:documentation-audit

Audit repository documentation against actual source code to identify gaps and drift.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/codingthefuturewithai/claude-code-primitives --skill devflow-docs-documentation-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devflow:docs:documentation-audit
Source: https://github.com/codingthefuturewithai/claude-code-primitives/tree/main/skills/docs/documentation-audit
Command: npx skills add https://github.com/codingthefuturewithai/claude-code-primitives --skill devflow-docs-documentation-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and update project documentation against actual source code. Use this to verify documentation is up-to-date with the codebase.

Core Features & Use Cases

  • Code → Docs verification: Ensure every significant component has corresponding documentation.
  • Docs → Code verification: Validate that documented claims match the codebase.
  • Layered discovery: Inspect repository structure to identify documentation gaps and drift.

Quick Start

Use the documentation-audit skill to begin a layer-by-layer audit of the repository starting from the root.

Frequently Asked Questions about devflow:docs:documentation-audit

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

FAQPage Schema
How do I audit my documentation against the actual codebase?

You can audit project documentation by running this skill to perform layer-by-layer discovery across your repository structure, enforcing bidirectional verification to surface drift and propose concrete doc edits.

What is bidirectional verification for documentation gaps?

Bidirectional verification for documentation gaps checks code to ensure every component has docs, and validates that documented claims match the codebase reality, preventing structural inconsistencies.

Why does my project documentation drift from the source code?

Project documentation drifts from source code when repository updates are not reflected in the docs. This skill inspects configurations and code to identify these inconsistencies and propose updates.

How do I find undocumented code components in my repository?

You find undocumented code components by applying code-to-docs verification, which inspects your repository structure layer-by-layer to ensure every significant component has corresponding documentation.

Can I automatically generate concrete edits for outdated documentation?

Yes, you can generate concrete edits for outdated documentation. The audit proposes specific edits or new docs to fix gaps while preserving the actual codebase reality.