Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claudemd
Use when CLAUDE.md files may be outdated — package versions changed, directories renamed, commands modified, or modules reference deleted files
npx claudepluginhub jugrajsingh/skillgarden --plugin claudemdHow this skill is triggered — by the user, by Claude, or both
Slash command
/claudemd:syncingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect drift between documented context and actual codebase state across ALL files: root, module-level, and .claude/rules/. Apply surgical updates.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Designs test strategies and plans with testing pyramid. Covers APIs, frontend, data pipelines, infrastructure; outputs plans including coverage targets, examples, and gaps.
Share bugs, ideas, or general feedback.
Detect drift between documented context and actual codebase state across ALL files: root, module-level, and .claude/rules/. Apply surgical updates.
find . -name 'CLAUDE.md' -not -path '*/node_modules/*' -not -path '*/venv/*' -not -path '*/target/*' -not -path '*/dist/*' 2>/dev/null
find .claude/rules -name '*.md' -type f 2>/dev/null
Classify each as Root, Module, or Rule. If no files found: "No context files to sync. Run /claudemd:init first."
Read all discovered files. For each file, note: level (root/module/rule), sections and their content, references to specific versions, paths, commands, and files.
Run tech stack, directory structure, available commands, linter config, module-level, and staleness signal checks in parallel. See references/drift-analysis.md for all bash commands.
Compare documented state vs reality across root, module, and rule drift dimensions. Classify each change as + (new), - (removed), or ~ (changed). See references/drift-analysis.md for dimension tables and classification symbols.
Show a sync report grouped by file, listing each drift item with symbol, description, and line reference. See references/report-templates.md for the full report format.
AskUserQuestion:
question: "How should I apply these changes?"
header: "Apply"
options:
- label: "Apply all (Recommended)"
description: "Update all drifted files automatically"
- label: "Review each"
description: "Step through each file for approval"
- label: "Preview only"
description: "Show proposed edits without applying"
For each approved change: edit specific lines in the affected file, preserve surrounding context and formatting, keep within size budgets per level. For orphaned module files: ask before deleting. For new qualifying directories: suggest /claudemd:init {path}.
Show updated files with change counts and line deltas, list unresolved items with suggested commands, and display context load totals per working directory. See references/report-templates.md for the full report format.
/claudemd:optimize)/claudemd:init {path})Sync is surgical: facts only, no restructuring.