Stats
Actions
Tags
From omo
Check if README.md and user guide reflect current project state — philosophy, features, agent models, skill list. Fix any drift. Activate when #sync appears anywhere in the user message.
How this skill is triggered — by the user, by Claude, or both
Slash command
/omo:docs-syncThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Sync documentation with current project state: $ARGUMENTS
Sync documentation with current project state: $ARGUMENTS
Step 1 — Gather current truth:
Read these source-of-truth files in parallel:
CLAUDE.md — philosophy, agent categories, skills, hooks, operating rules.claude-plugin/plugin.json — version, descriptionscripts/init-config.sh — default config values (model defaults, feature flags)hooks/hooks.json — registered hook eventsskills/*/SKILL.md for the full skill list (name, shortcut, description)agents/*.md for agent list (name, model, category)Step 2 — Diff against docs:
Read and compare:
README.mddocs/user-guide.md (if exists)docs/config.md (if exists)For each doc, check:
.claude/state/ listing complete?Step 3 — Report drift:
List each discrepancy as:
[file:line] WHAT_IS → WHAT_SHOULD_BECategorize as:
Step 4 — Fix:
docs-keeper to draft the content.Step 5 — Verify:
After edits, verify:
End with:
npx claudepluginhub speson/omo --plugin omoAudits codebase documentation against actual behavior, producing a severity-tagged drift report (STALE, MISSING, OUTDATED, DUPLICATE). Read-only review.
Scans .claude/ directories for skills, commands, and agents, extracts metadata, compares to existing CLAUDE.md files, and updates documentation by adding missing entries, removing stale ones, and fixing counts.
Synchronizes project docs (CLAUDE.md, README.md, architecture.md) with code state via quality scoring (0-100), gap analysis, skill/ADR audits using git log, and change reports. Use for doc-code alignment.