Learn-skills.dev doc-sync
Audit project documentation against the codebase and fix drift. Run before PRs or after major changes. Compares documented architecture, test counts, and file paths against actual state.
install
source · Clone the upstream repo
git clone https://github.com/NeverSight/learn-skills.dev
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/acedergren/agentic-tools/doc-sync" ~/.claude/skills/neversight-learn-skills-dev-doc-sync && rm -rf "$T"
manifest:
data/skills-md/acedergren/agentic-tools/doc-sync/SKILL.mdsource content
Documentation Sync Audit
Audit all project documentation against the actual codebase and report (or fix) any drift.
Steps
-
Identify documentation files: Find all
files in.md
, project root, anddocs/
that describe architecture, security, testing, or roadmap..claude/reference/ -
Audit architecture docs against the codebase:
- Check main entry point — does the plugin/middleware chain match the documented order?
- Check routes directory — are all route modules listed?
- Check shared packages — are all exports documented?
- Check monorepo layout — does the documented tree match actual directory structure?
-
Audit security docs:
- Check security plugins/middleware — are all documented?
- Check for new security-related commits since last doc update
- Verify permission counts match actual definitions
-
Audit test docs:
- Count actual test files
- Run test suite to get current pass counts
- Compare documented test counts to actual counts
-
Audit roadmap/changelog:
- Check git log for commits not reflected in any documented phase
- Verify completed phases are marked done
-
Audit CLAUDE.md / agent instructions:
- Check naming conventions match actual code patterns
- Verify documented file paths still exist
- Confirm anti-patterns section is current
-
Report findings:
| Doc | Section | Issue | Severity | |-----|---------|-------|----------| -
Fix drift (if
contains "fix"):$ARGUMENTS- Make targeted edits to fix each drift item
- Commit with
docs: sync documentation with codebase [doc-sync]
If
$ARGUMENTS is empty or "audit", only report — don't edit.
Arguments
:$ARGUMENTS
(default, report only) oraudit
(report and fix drift)fix
When to Run
- Before creating a pull request (
)/doc-sync audit - After completing a development phase (
)/doc-sync fix - After any structural changes (new plugins, routes, migrations)