doc-audit

To scan markdown documentation for broken links and frontmatter errors, run an automated health check that detects schema violations, mismatched count claims, and stale version references to generate a severity-categorized audit report.

You can detect stale version references in technical docs by running an automated documentation audit that flags outdated version numbers and mismatched count claims, ensuring project content remains accurate and accessible for end users.

Yes, you can automate documentation checks before a release by running a full health scan on your docs directory to catch broken internal links, frontmatter violations, and outdated version references that would otherwise confuse contributors.

The best way to find broken internal links in project markdown files is using an automated documentation audit tool that generates line-specific issue details within a persistent markdown report for fast remediation.

Yes, the doc-audit skill flags broken documentation builds on the main branch by automating the detection of frontmatter violations, broken internal links, count claim drift, and stale version references during pre-release validation.