docs-analyze

To audit documentation for accuracy and staleness, the Skill cross-checks doc claims against real source code and uses git log comparisons to quantify update drift, producing a prioritized quality report with per-file scorecards and recommended fixes.

Documentation staleness occurs when recent commits for relevant code paths outpace the last update time of each doc. This Skill detects drift by comparing git log changes against doc modifications to flag outdated files.

To find coverage gaps in your project documentation, this Skill inventories your docs/ files and identifies modules or features that exist in the codebase but have no corresponding documentation file.

Yes, you can check documentation health for a specific file, a named component, or the entire docs directory. The Skill scopes its source code cross-checking and git log change tracking to the target you specify.

Yes, the documentation quality report includes recommended fixes. It provides prioritized per-file scorecards that flag contradictions with source code, coverage gaps, and staleness drift to guide corrections.