Sync docs
Skill joaquimscosta/arkhe-claude-plugins/.claude/skills/sync-docs
Supercharge Claude Code with 109 specialized components — 22 agents, 32 commands, 55 skills across 13 modular plugins. Deep reasoning, autonomous dev loops, DDD architecture, design system enforcement, git automation, and more.
npx -y skills add joaquimscosta/arkhe-claude-plugins --skill sync-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Sync official Anthropic documentation and analyze impact on project components. Runs docs/reference/update-claude-docs.sh, computes diffs, and reports impacts on the skill validator, plugins, and project documentation. Use when user mentions "sync docs", "update reference docs", "refresh docs", or "check doc changes".
SKILL.md
3.8 KB, 812 tokens by cl100k_base, as published. Nobody here has run it
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