doc-sync

Detect drift between cc-ref-* skills and live Anthropic documentation.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill doc-sync-usernametron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-sync
Source: https://github.com/UsernameTron/Claude-Code-Kickstart/tree/main/plugins/claude-code-factory/skills/doc-sync
Command: npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill doc-sync-usernametron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps cc-ref-* reference skills aligned with live Anthropic documentation, preventing drift and stale references.

Core Features & Use Cases

  • Drift detection across all cc-ref-* reference skills against code.claude.com docs.
  • Two-mode operation: check (report only) and patch (apply updates with approval).
  • Supports per-skill or full-registry scope; integrates with the doc-sync-checker subagent.

Quick Start

Run /sync-docs to check all reference skills, or /sync-docs patch to apply approved updates.

Frequently Asked Questions about doc-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect documentation drift between reference skills and live Anthropic docs?

Documentation drift is detected by comparing cc-ref-* reference skills against live Anthropic documentation on code.claude.com. The doc-sync-checker subagent scans all or targeted skills to report discrepancies without applying changes.

How do I patch stale reference docs to match live Anthropic documentation?

To patch stale reference docs, run the patch mode workflow which applies updates to cc-ref-* skills with approval. This updates the url-registry and related metadata to align with live Anthropic documentation.

Can I check documentation drift for a single skill instead of the entire registry?

Yes, documentation drift detection supports per-skill or full-registry scope. You can target a specific cc-ref-* skill to check or patch rather than scanning the entire reference skill set.

What is the difference between check and patch modes for documentation sync?

Check mode reports documentation drift only, while patch mode applies updates with approval. Both modes operate across all cc-ref-* reference skills or targeted ones against live Anthropic docs.

Why does my reference skill documentation show outdated Anthropic API information?

Outdated information occurs when cc-ref-* reference skills drift from live Anthropic documentation on code.claude.com. Running a drift detection check identifies these stale references for patching.