docs-reviewer

Documentation freshness checks detect whether your docs reflect recent code changes by tracing modifications and surfacing stale sections. This validates that your codebase documentation aligns with current APIs and code behavior.

A documentation coverage audit identifies undocumented areas across your codebase to ensure documentation breadth. It scans your codebase and reports gaps in documentation, providing concrete guidance for remediation.

Yes, you can validate documentation accuracy during code reviews by comparing documentation against actual code behavior and APIs. This enforces that documentation aligns with code and surfaces incorrect docs before release.

Automated documentation health checks for pre-release audits validate freshness, accuracy, and coverage across your codebase. They trace code changes, report documentation gaps, and provide concrete remediation guidance.

Documentation goes stale when it falls out of sync with code changes over time. You detect stale documentation by tracing recent codebase modifications and validating that existing docs accurately reflect current code behavior and APIs.

No specific dependencies are required to perform a documentation quality audit. The process validates documentation freshness, accuracy, and coverage natively by comparing docs against actual code behavior and APIs across your codebase.