sync-docs
Sync Docs
Sync official Anthropic documentation into docs/reference/ and produce an impact analysis report.
Quick Start
Run the sync and diff script:
scripts/sync_and_diff.py
Preview changes without overwriting:
scripts/sync_and_diff.py --dry-run
Execution
Phase 1: Sync & Diff
- Execute
scripts/sync_and_diff.py(or with--dry-runif$ARGUMENTScontains--dry-run) - Parse the JSON output from stdout
- Display a summary table of changed/unchanged files
Phase 2: Impact Analysis
For each changed file, perform the following analysis. See WORKFLOW.md for detailed steps.
2a. Skill Validator Impact (CRITICAL priority)
Check discrepancies in the JSON output:
skill_frontmatter_keys.in_docs_not_validator(CRITICAL): New fields in SKILLS.md the validator will reject as unknown (FM009). Report exact fields and line invalidate_skill.pyto update (ALLOWED_FRONTMATTER_KEYS, ~line 151).skill_frontmatter_keys.in_validator_not_docs(WARNING): Fields the validator allows but SKILLS.md no longer documents. May be from SUBAGENTS.md (valid forcontext: fork) or deprecated.subagent_frontmatter_keys(INFO): New subagent fields from SUBAGENTS.md. Not all are valid in skill frontmatter — report for context. Only flag fields that overlap with skill usage (e.g.,maxTurns,mcpServers,memory,skills).hook_events.in_docs_not_validator(CRITICAL): New hook events the validator will reject (HK001). Report the line to update (VALID_HOOK_EVENTS, ~line 1021).hook_events.in_validator_not_docs(WARNING): Hook events the validator knows but docs no longer list.memory_scopes: Review manually if SUBAGENTS.md changed — check if memory scope options expanded.
2b. Plugin Component Impact (WARNING priority)
For each changed synced doc, identify the conceptual areas that changed (new fields, deprecated features, renamed concepts). Then:
- Use Grep to search
plugins/*/for references to changed concepts - Flag plugins using deprecated patterns
- Note new capabilities not yet leveraged (as INFO)
2c. Project Documentation Impact (WARNING priority)
Check these files for stale references to synced doc content:
CLAUDE.md— Plugin Component Guidelines section, Key Documentation Files sectiondocs/README.md— Synced Documentation section, learning pathsdocs/SKILL_DEVELOPMENT_BEST_PRACTICES.md— Frontmatter reference, patterns
Output Format
Present findings as a structured report:
=== Documentation Sync Impact Report ===
## Sync Summary
| File | Status | +Lines | -Lines | New Sections | Removed Sections |
|------|--------|--------|--------|--------------|-----------------|
...
## CRITICAL: Skill Validator Updates Required
(List each discrepancy with file, line number, and fix)
## WARNING: Plugin Components Affected
(List affected plugins and what changed)
## WARNING: Project Documentation Stale
(List affected doc files and what to update)
## INFO: New Capabilities Available
(List new features from updated docs that could be leveraged)
If no files changed, report: "All documentation is up to date. No impacts detected."
References
- WORKFLOW.md — Detailed impact analysis steps
- EXAMPLES.md — Example report outputs
- TROUBLESHOOTING.md — Common issues
More from joaquimscosta/arkhe-claude-plugins
skill-validator
Validate skills against Anthropic best practices for frontmatter, structure, content, file organization, hooks, MCP, and security (62 rules in 8 categories). Use when creating new skills, updating existing skills, before publishing skills, reviewing skill quality, or when user mentions "validate skill", "check skill", "skill best practices", "skill review", or "lint skill".
30domain-driven-design
Expert guidance for Domain-Driven Design architecture and implementation. Use when designing complex business systems, defining bounded contexts, structuring domain models, choosing between modular monolith vs microservices, implementing aggregates/entities/value objects, or when users mention "DDD", "domain-driven design", "bounded context", "aggregate", "domain model", "ubiquitous language", "event storming", "context mapping", "domain events", "anemic domain model", strategic design, tactical patterns, or domain modeling. Helps make architectural decisions, identify subdomains, design aggregates, and avoid common DDD pitfalls.
26code-explanation
Explains complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Use when user asks to explain code, understand algorithms, analyze design patterns, wants code walkthroughs, or mentions "explain this code", "how does this work", "code breakdown", or "understand this function".
22generating-changelog
Analyzes git commit history and generates professional changelogs with semantic versioning, conventional commit support, and multiple output formats (Keep a Changelog, Conventional, GitHub). Use when editing CHANGELOG.md, CHANGELOG.txt, or HISTORY.md files, preparing release notes, creating releases, bumping versions, updating changelog, documenting changes, writing release notes, tracking changes, version bump, tag release, or when user mentions "changelog", "release notes", "version history", "release", "semantic versioning", or "conventional commits".
21workflow-orchestration
>
19generating-stitch-screens
>
19