doc-verification

Documentation verification analyzes your codebase to check completeness, accuracy, consistency, and quality of your docs. It cross-references README files, API references, and architecture docs against the actual code to identify misalignments and missing sections.

Evidence-backed documentation auditing enforces traceable claims by requiring exact file references, change history, and documented reasoning during analysis. It generates structured reports with file and line references to ensure every documented claim is verifiable against the codebase.

Freshness assessment detects outdated or deprecated content and references by analyzing your documentation files. It scans README files, API references, and architecture docs to flag stale information, deprecated features, and outdated cross-references that no longer match the current codebase.

Consistency validation enforces terminology alignment, cross-references, and link integrity across multiple documentation files. It checks that terms are used uniformly and that all internal and external links within your docs remain valid and correctly point to their intended targets.

Completeness checks identify missing sections and unresolved TODOs across README files, API references, and architecture docs. The verification process scans for incomplete documentation areas, ensuring all necessary sections are present and properly filled out without lingering placeholders.

Documentation verification operates with no external dependencies or component installations required. It functions as a standalone skill that directly analyzes your codebase documentation, cross-references related files, and generates evidence-based reports without needing additional tools or plugins.