documentation-audit

Run a full documentation audit on your target repository to quantify drift. It identifies outdated information, broken links, and missing sections across key docs like README.md and ARCHITECTURE.md, producing a committed severity-annotated log with a summary.

Documentation drift occurs when project docs contain outdated information and broken links. This skill quantifies drift by scanning files like CHANGELOG.md and SKILL.md, producing a structured audit log with severity ratings and actionable items.

You can check for broken links and missing sections by running this audit skill across your markdown files. It references an audit-log template to ensure consistent reporting and outputs a comprehensive severity-annotated log.

Yes, you can integrate a documentation audit into onboarding and release processes to keep docs in sync with code. It generates a committed audit log with severity ratings and a summary to track documentation health.

The best way to generate a severity-annotated audit log is to run a full documentation audit on your repository. It references an audit-log template to ensure consistent reporting and outputs a committed log with a summary.

No, you do not need any dependencies to run this documentation audit. It operates without external dependencies and references an internal audit-log template to produce a structured drift report with severity ratings.