doc-audit

Detect documentation drift by running a static audit that parses markdown and frontmatter to identify broken relative links, code-block syntax issues, and outdated ADRs. It produces a structured report without executing external requests.

Check markdown files by executing a static documentation audit that uses pattern matching for relative-link resolution and code-block validity. The process yields a structured report detailing these errors without live network requests.

Yes, you can audit architecture decision records (ADRs) for freshness within a static docs directory. The analysis cross-checks ADR files against the README and project documentation to highlight misaligned or outdated decisions.

Yes, the documentation audit supports stack-specific hints for node-ts, python, and swift. It cross-checks your repository documentation against technical stack guidance to ensure accuracy across these environments.

The best way to find outdated placeholders and doc hints is using a static analysis audit. It evaluates repository documentation through markdown parsing and pattern matching, ensuring no external requests are executed during the review.

A limitation of static documentation analysis is that it operates exclusively on static docs within code repositories and does not execute external requests. It relies entirely on markdown parsing and pattern matching to identify drift.