audit-docs

Audit repository documentation for duplication, staleness, language issues, and verbosity.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill audit-docs-dgouron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-docs
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/audit-docs
Command: npx skills add https://github.com/DGouron/review-flow --skill audit-docs-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit documentation across a repository to identify duplication, staleness, language issues, and verbosity. Read-only — produces an actionable report.

Core Features & Use Cases

  • Duplication detection across docs and README files to prevent content drift.
  • Staleness checks using last-updated timestamps and related links to surface outdated content.
  • Language consistency enforcement by flagging non-English content and tone issues.
  • Verbosity analysis with actionable recommendations to condense long sections.
  • Generates a structured audit report that teams can act on to improve documentation quality.

Quick Start

Run the audit on your docs folder to generate a comprehensive report.

Frequently Asked Questions about audit-docs

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

FAQPage Schema
How do I audit documentation for duplication and staleness across a repository?

To audit documentation for duplication and staleness, you run a scan across your repository to identify content drift and outdated sections. It checks last-updated timestamps, related links, and cross-file consistency to produce an actionable quality report.

What is documentation verbosity analysis and how does it help maintainability?

Documentation verbosity analysis identifies overly long sections and provides actionable recommendations to condense content. By flagging unnecessary length and tone issues, it improves readability and long-term maintainability of large document collections.

Can I enforce language consistency and frontmatter presence in multi-format docs?

Yes, you can enforce language consistency and frontmatter presence across multi-format sources. The audit detects non-English content, flags tone issues, and validates that required frontmatter fields exist to ensure standardized documentation governance.

Does documentation auditing work for large document collections with multiple file formats?

Documentation auditing is specifically applicable to large document collections and multi-format sources. It performs automated quality checks across diverse files and generates a structured report teams can act on for governance.

What is the best way to generate a structured report for documentation quality and cross-file consistency?

The best way to generate a structured report for documentation quality is to run an automated audit enforcing checks for frontmatter, cross-file consistency, and staleness indicators. This read-only process produces actionable governance insights.