documentation-audit
This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.
Best use case
documentation-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.
This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "documentation-audit" skill to help with this workflow task. Context: This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/documentation-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How documentation-audit Compares
| Feature / Agent | documentation-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill should be used when verifying documentation claims against codebase reality. Triggers on "audit docs", "verify documentation", "check docs", "docs accurate", "documentation drift", "before release", "after refactor", "docs don't match". Uses two-pass extraction with pattern expansion for comprehensive detection.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
SKILL.md Source
<!-- ABOUTME: Documentation audit skill for verifying claims against codebase --> <!-- ABOUTME: Uses two-pass extraction with pattern expansion for comprehensive detection --> # Documentation Audit Systematically verify claims in documentation against the actual codebase using a two-pass approach. ## Overview **Core principle:** Low recall is worse than false positives—missed claims stay invisible. **Two-pass process:** 1. **Pass 1:** Extract and verify claims directly from docs 2. **Pass 2A:** Expand patterns from false claims to find similar issues 3. **Pass 2B:** Compare codebase inventory vs documented items (gap detection) ## Quick Start 1. Identify target docs (user-facing only, skip `plans/`, `audits/`) 2. Note current git commit for report header 3. Run Pass 1 extraction using parallel agents (one per doc) 4. Analyze false claims for patterns 5. Run Pass 2 expansion searches 6. Generate `docs/audits/AUDIT_REPORT_YYYY-MM-DD.md` ## Claim Types | Type | Example | Verification | |------|---------|--------------| | `file_ref` | `scripts/foo.py` | File exists? | | `config_default` | "defaults to 'AI Radio'" | Check schema/code | | `env_var` | `STATION_NAME` | In .env.example + code? | | `cli_command` | `--normalize` flag | Script supports it? | | `behavior` | "runs every 2 minutes" | Check timers/code | **Verification confidence:** - **Tier 1 (auto):** file_ref, config_default, env_var, cli_command - **Tier 2 (semi-auto):** symbol_ref, version_req - **Tier 3 (human review):** behavior, constraint ## Pass 2 Pattern Expansion After Pass 1, analyze false claims and search for similar patterns: ``` Dead script found: diagnose_track_selection.py → Search: all script references → Found 8 more dead scripts Wrong interval: "every 10 seconds" → Search: "every \d+ (seconds?|minutes?)" → Found 3 more Wrong service name: ai-radio-break-gen.service → Search: service/timer names → Found naming inconsistencies ``` **Common patterns to always check:** - Dead scripts: `scripts/*.py` references - Timer intervals: `every \d+ (seconds?|minutes?)` - Service names: `ai-radio-*.service`, `*.timer` - Config vars: `RADIO_*` environment variables - CLI flags: `--flag` patterns in bash blocks ## Output Format Generate `docs/audits/AUDIT_REPORT_YYYY-MM-DD.md`: ```markdown # Documentation Audit Report Generated: YYYY-MM-DD | Commit: abc123 ## Executive Summary | Metric | Count | |--------|-------| | Documents scanned | 12 | | Claims verified | ~180 | | Verified TRUE | ~145 (81%) | | **Verified FALSE** | **31 (17%)** | ## False Claims Requiring Fixes ### CONFIGURATION.md | Line | Claim | Reality | Fix | |------|-------|---------|-----| | 135 | `claude-sonnet-4-5` | Actual: `claude-3-5-sonnet-latest` | Update | ## Pattern Summary | Pattern | Count | Root Cause | |---------|-------|------------| | Dead scripts | 9 | Scripts deleted, docs not updated | ## Human Review Queue - [ ] Line 436: behavior claim needs verification ``` ## Detailed References For execution checklist and anti-patterns: [checklist.md](checklist.md) For claim extraction patterns: [extraction-patterns.md](extraction-patterns.md)
Related Skills
audit-website
Audit websites for SEO, technical, content, and security issues using squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use when analyzing websites, debugging SEO issues, or checking site health.
wcag-audit-patterns
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
seo-content-auditor
Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines. Use PROACTIVELY for content review.
security-auditor
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and incident response. Use PROACTIVELY for security audits, DevSecOps, or compliance implementation.
production-code-audit
Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
laravel-security-audit
Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.
documentation-templates
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
documentation-generation-doc-generate
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
dependency-management-deps-audit
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
codebase-cleanup-deps-audit
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
code-documentation-doc-generate
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
code-documentation-code-explain
You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations.