Can I use this with any tech stack?

Yes, it is stack-agnostic but includes a 'Stack Adaptation' check to ensure that references and external links are appropriate for your specific platform.

How does the auditor verify 'Actuality'?

It cross-references documentation paths, function names, and APIs directly against the source code to identify mismatches or outdated instructions.

Why does it recommend removing code blocks from documentation?

To prevent duplication and maintenance debt. It encourages using tables, diagrams, or direct links to source code files where the implementation lives.

What is the primary entry point for the documentation audit?

It treats CLAUDE.md as the root of the project's documentation hierarchy and builds its audit tree based on outward links from that file.

Documentation Auditor & Quality Optimizer

Name: Documentation Auditor & Quality Optimizer
Author: levnikolaevich

bylevnikolaevich

•

콘텐츠 관리

Audits project documentation against six quality categories to ensure accuracy, eliminate redundancy, and maintain a single source of truth.

The ln-600-docs-auditor is a specialized skill for Claude Code designed to maintain high-quality project documentation. It scans Markdown files starting from the CLAUDE.md root, evaluating them for structural integrity, factual accuracy against actual code, and proactive compression. By enforcing a 'Single Source of Truth' and removing redundant code blocks in favor of structured tables or direct links, it ensures that documentation remains a lightweight, reliable, and actionable resource throughout the development lifecycle.

주요 기능

01Factual verification of documentation against the current codebase to prevent misleading info

02Automated scoring system (X/10) with detailed findings and prioritized recommended actions

0338 GitHub stars

04Proactive content compression that replaces verbose prose with structured tables and ASCII diagrams

056-Category Quality Audit covering Hierarchy, SSOT, Compression, Requirements, Actuality, and Legacy content

06Stack-specific adaptation to ensure technical references match your project's primary language

사용 사례

01Standardizing documentation across a multi-repo organization to ensure consistent hierarchy

02Reviewing documentation quality after major project refactors or architectural changes

03Cleaning up legacy 'history' notes and outdated prose to focus on the current project state

주요 기능

01Factual verification of documentation against the current codebase to prevent misleading info

02Automated scoring system (X/10) with detailed findings and prioritized recommended actions

0338 GitHub stars

04Proactive content compression that replaces verbose prose with structured tables and ASCII diagrams

056-Category Quality Audit covering Hierarchy, SSOT, Compression, Requirements, Actuality, and Legacy content

06Stack-specific adaptation to ensure technical references match your project's primary language

사용 사례

01Standardizing documentation across a multi-repo organization to ensure consistent hierarchy

02Reviewing documentation quality after major project refactors or architectural changes

03Cleaning up legacy 'history' notes and outdated prose to focus on the current project state