What problem does it solve? Documentation drifts out of sync with code over time: frontmatter fields go missing, internal links break, claimed counts of agents or features become wrong, and version references go stale. This Skill automates a four-category health audit of markdown docs and produces a persistent report so issues are caught before they reach a PR. ## Core Features & Use Cases - Four-Category Static Scan: Checks frontmatter schema compliance, broken internal links, count claim drift, and stale version references against declared ranges. - Structured Reporting: Prints a terminal summary table with PASS/WARN/ERROR status per category and writes a persistent docs/audit-report.md with per-finding details including file and line numbers. - Docs Build Verification: Optionally runs mkdocs build --strict against main to catch docs build regressions that path-filtered CI jobs miss. - Use Case: Before merging a docs-touching PR, run the audit to confirm no broken links or stale Python version references exist, and fix the flagged findings at the source. ## Quick Start Ask the AI to run a documentation health audit on the docs directory and report any broken links, frontmatter violations, or stale version references. ## Quick Start Run the doc audit on your docs folder to get a summary table and a written report of all findings.
