What problem does it solve?
Many repository documentation files become stale, inconsistent, or incomplete as code, releases, and processes evolve. This Skill provides a systematic, evidence-first audit to uncover incorrect claims, missing changelog entries, broken links, and status drift across user-facing and operational docs so maintainers can prioritize precise fixes.
Core Features & Use Cases
- Evidence-backed findings: For each issue produce a claim (verbatim quote with file:line), evidence (git output, file listing, or code grep), and a specific remediation recommendation.
- Scoped auditing: Targets repo-root docs, spaceui docs, package CHANGELOGs, nested CLAUDE.md files, .claude/rules, openspec specs, and other Tier 1/2 files while honoring explicit out-of-scope directories like vendored spacedrive.
- Release and lifecycle checks: Verify CHANGELOG completeness vs commits and queued changesets, validate version/date claims against manifests, and flag links to gitignored/transient paths.
- Use case: Run after a merge wave or before a release to produce a prioritized report of incorrect, stale, and missing documentation items.
Quick Start
Run an evidence-backed documentation audit across the repository and produce a prioritized findings report with file and git citations.