Ln 600 Docs Auditor

What it does

The Ln 600 Docs Auditor skill analyzes project documentation to ensure clarity, consistency, and accuracy. It proactively identifies opportunities to reduce document size while maintaining value, eliminates redundancy, converts prose into structured formats like tables and lists, and verifies the overall documentation hierarchy rooted at CLAUDE.md. Crucially, it also delegates semantic verification to the ln-601 skill to ensure content aligns with project scope and the codebase reality.

When to use it

• Quality Review: To proactively assess the quality of existing project documentation.
• Documentation Pipeline Integration: As part of an automated document processing pipeline (specifically, Phase 5 of ln-100-documents-pipeline when auditDocs=true).
• Standardization Enforcement: To ensure documentation adheres to established standards and best practices within a project.
• Codebase Synchronization: To verify that documentation accurately reflects the current state of the codebase.

Key capabilities

• Structural Checks: Verifies documentation hierarchy, links (ensuring no orphaned or broken links), and adherence to root file (CLAUDE.md).
• Single Source of Truth Enforcement: Detects and eliminates content duplication, replacing them with links to source documents.
• Content Compression: Identifies verbose or redundant content for removal and suggests converting prose into structured formats.
• Semantic Verification Delegation: Delegates semantic content auditing to the ln-601-semantic-content-auditor skill.
• Actuality Checks: Validates factual accuracy against the codebase (e.g., verifying paths, function names, and API validity).
• Legacy Cleanup: Removes outdated information such as historical notes or deprecated content.

Example prompts

• "Audit the documentation for clarity and consistency."
• "Run a full quality audit of all markdown files in the project."
• "Check the CLAUDE.md file and related documents for broken links and duplication."

Tips & gotchas

• Root Directory: The skill expects file paths to be relative to the skills repository root. If running from a different directory, navigate up one level before invoking.
• Semantic Audit Dependency: The semantic audit component relies on the ln-601-semantic-content-auditor skill being installed and functional.
• Excluded Directories: The skill excludes documents within the docs/tasks/, docs/reference/, docs/presentation/, and tests/ directories from its analysis.