Detect documentation drift between project docs and repository code.
npx skills add https://github.com/cacack/my-family --skill audit-docs-cacack
Please help me install this Agent Skill. Skill: audit-docs Source: https://github.com/cacack/my-family/tree/main/.claude/skills/audit-docs Command: npx skills add https://github.com/cacack/my-family --skill audit-docs-cacack
Project documentation often diverges from the actual repository state, causing onboarding friction, incorrect developer assumptions, and broken build or deployment expectations. This Skill performs a focused, read-only comparison between documentation and code to surface missing files, stale technology lists, inconsistent convention references, and broken internal links.
Perform a read-only audit that compares CLAUDE.md, docs/CONVENTIONS.md, docs/INTEGRATION-MATRIX.md, go.mod, web/package.json, internal/ and internal/repository/ directory contents, and generated API artifacts, then produce the structured Doc-Drift Audit Report.
High-intent search queries and answers about installing and using this skill.
To detect documentation drift, you can run a read-only audit that compares project markdown files like CLAUDE.md and docs/CONVENTIONS.md against the actual repository codebase to surface missing files, stale dependencies, and inconsistent references.
You can check if technical documentation matches project dependencies by parsing go.mod and web/package.json, then cross-referencing the listed technologies against the dependencies documented in CLAUDE.md and CONVENTIONS.md to find stale or undocumented packages.
Your integration matrix may list event types missing from the codebase due to documentation drift, which happens when internal/repository/eventstore.go and readmodel.go structs are updated without syncing changes back to docs/INTEGRATION-MATRIX.md.
To validate relative markdown links, you can perform a read-only audit that checks link integrity within the audited docs and verifies that commit and convention references correctly point to docs/CONVENTIONS.md as the canonical source.
Yes, you can audit generated API artifacts like internal/api/openapi.yaml and directory trees without modifying the repository, because the documentation drift detection requires read-only access to list directories, open files, and parse dependency files.
The best way to find undocumented directories in your internal codebase is to extract the internal/ directory tree described in CLAUDE.md and compare it against the actual internal/* and internal/repository/* directory listings to identify missing entries.
botminterList BotMinter teams, members, roles, workspaces, and running state from local configs.
OmarHosamCodesAudit Obsidian vaults for orphaned pages, broken links, and frontmatter issues.
JasonLoAudit codebase syntax and API usage against dependency documentation.
fengshao1227Validate software module directory structures and documentation completeness.
