devflow:docs:reference-audit

Scan Markdown files and docs directories to produce a discrepancy list and synchronization plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies documentation gaps and aligns docs with the current codebase, ensuring consistency across the repository.

Core Features & Use Cases

  • Documentation discovery: Locate markdown files, docs directories, and inline documentation across the project.
  • Consistency auditing: Compare docs against code references to surface discrepancies and stale content.
  • Synchronization planning: Generate a concrete plan to reconcile documentation with the codebase, including a discrepancy list and update roadmap.

Quick Start

Run the documentation reference audit to scan the repository and generate a synchronization plan.

Frequently Asked Questions about devflow:docs:reference-audit

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

FAQPage Schema
How do I find documentation discrepancies between my markdown files and the codebase?

To find documentation discrepancies, you can scan Markdown files, docs directories, and README references against the codebase to surface stale content and generate a list of inconsistencies.

What is the best way to plan synchronization updates for outdated project documentation?

Planning synchronization updates involves scanning repository documentation to identify gaps and generating an actionable roadmap that aligns project docs with the current codebase.

Does the documentation audit scan in-code comments and README references for inconsistencies?

Yes, the documentation audit scans Markdown files, docs directories, README references, and in-code comments to locate documentation gaps and surface discrepancies across the repository.

How do I audit inline documentation across my repository to ensure consistency?

You can audit inline documentation by scanning the project's docs directories and codebase to compare references, surfacing discrepancies and planning updates for repository-wide consistency.

When do I need to run a documentation reference audit on my repository?

You need to run a documentation reference audit when project docs are suspected to be out of sync with the codebase, requiring a scan of Markdown files to produce a discrepancy list and update plan.