Audit repository documentation against code and active plans to surface drift.
npx skills add https://github.com/mjamore/repo-docs-skill --skill repo-docs-audit
Please help me install this Agent Skill. Skill: repo-docs-audit Source: https://github.com/mjamore/repo-docs-skill/tree/main/repo-docs-audit Command: npx skills add https://github.com/mjamore/repo-docs-skill --skill repo-docs-audit
Audit repository documentation against code and active plans to surface drift and misalignment between docs, plans, and implementation. This helps ensure that the documentation remains the single source of truth and aligns with the actual code changes.
/docs, /docs/plans, and the codebase.Run a lightweight audit on the current workspace to surface concrete repo-docs and code inconsistencies.
High-intent search queries and answers about installing and using this skill.
To detect documentation drift, audit repository docs against code and active plans to surface misalignment. This verifies that progress documentation and specs reflect the current implementation by reporting outdated items and conflicting states.
The best way to verify archiving readiness is auditing docs to ensure plan and spec links stay current. This surfaces missing links and stale references, confirming active plans align with recent source file changes before archiving.
You audit WORK_IN_PROGRESS.md by comparing it alongside linked plan and spec docs against recent code changes. This enforces that progress documentation reflects current implementation and reports any missing or outdated items.
Repository documentation shows conflicting states when active plans and specs are not updated alongside implementation. Auditing docs against code surfaces these misalignments, broken links, and stale references to restore alignment.
Yes, you can use a docs audit to find broken links and missing documentation. It compares linked plan and spec docs against source files to identify stale references and missing items that block accurate repository reviews.
paradox123Collect repository structure, runnable commands, and architecture anchors at startup.
MicrockValidate and align project documentation with the current codebase.
mjamoreSynchronize repository documentation with source code using doc-first workflows.
barrydobsonValidate links, naming, cross-references, and INDEX coverage in a skills wiki.