Stats
Actions
Tags
From sjh-skills
Checks whether project documentation is up-to-date after code changes by scanning git diffs and reporting stale or missing docs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sjh-skills:sync-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check recent code changes (`git diff HEAD~5 --name-only`), scan the project's documentation system, and report what needs updating.
Check recent code changes (git diff HEAD~5 --name-only), scan the project's documentation system, and report what needs updating.
Checklist items (detect based on directories that actually exist in the project):
docs/knowledge/ have new learnings to record?CLAUDE.md index table cover all knowledge files?docs/knowledge/ (dated entries with detail and rationale). Promote to .claude/rules/ only when a constraint is stable, imperative, and reused, and keep the rule to trigger + hard constraint + copy-paste exact values + a > Detail: pointer. Dated experience, measured numbers, and run tags (smoke vN / image tags) stay in knowledge, never in a rule.docs/strategy/ exists) — Do vision, roadmap, or paper-outline reflect recent changes? Compare git log activity against strategy doc last-modified dates. Flag docs that haven't been updated in 5+ commits of relevant code changes. Pair with /project-review for full strategic analysis..claude/rules/: any rule that has grown into a dated changelog, duplicates the project's main instructions (CLAUDE.md / AGENTS.md), or carries detail that belongs in knowledge → flag for prune. Sync is bidirectional — prune as well as add, not monotonic growth.Output a checklist marking each item as "needs update" or "up to date". Report only — do NOT auto-modify.
npx claudepluginhub jiahao-shao1/sjh-skills --plugin sjh-skillsImplements two-phase workflow to analyze code changes via git diff and update project documentation. Use before merging branches, after features/bugfixes, or when docs stale.
Audits codebase documentation against actual behavior, producing a severity-tagged drift report (STALE, MISSING, OUTDATED, DUPLICATE). Read-only review.
Detects documentation drift, stale references, and cross-document inconsistencies in projects. Scans code-doc mismatches, broken links, outdated versions, and git staleness.