cc-sync

cc-sync — Claude Code Changelog Sync

Track the official Claude Code changelog and keep cc-settings (schemas, config, hooks, agents, docs) in sync with new features. Removes anything that duplicates native functionality.

This is run on a weekly cadence. The mechanical parts are scripted; the judgment calls (which features to adopt, what counts as duplication) require human review at the gate.

Before you start

Always run from the cc-settings repo root. If you're not there, ask the user where it is — don't guess.

pwd  # should end in /cc-settings
git status  # tree must be clean before starting

If the tree is dirty, ask the user to commit or stash first. Sync work needs a clean baseline so the diff is reviewable.

Phase 1 — Detect drift

bun run upstream:scan

This compares upstream/claude-code-manifest.json against the live @anthropic-ai/claude-code npm version. Two outcomes:

• No drift — manifest matches live. Stop here. There's nothing to sync. Tell the user "already in sync at v" and end.
• Drift detected — capture both versions. Format: manifest=A → live=B.

Phase 2 — Fetch the upstream changelog

Fetch the official changelog and extract entries between the manifest version (exclusive) and the live version (inclusive):

WebFetch url: https://raw.githubusercontent.com/anthropics/claude-code/main/CHANGELOG.md
prompt: Extract entries for versions <A+1> through <B> verbatim. List each
        version's bullet points exactly as written.

Do not paraphrase. Quote the upstream bullets verbatim — the user needs to see exactly what was said upstream to validate your categorization.

Phase 3 — Cross-reference cc-settings

For each upstream change, decide which bucket it falls into. Read these files to inform the decision (use parallel tool calls):

Bucket	What to check
Settings keys	src/schemas/settings.ts (zod schema, strict — drift fails parse)
Hook events / types	src/schemas/hooks.ts (5-arm discriminated union as of v10.3.0)
MCP fields	src/schemas/mcp.ts (shared mcpCommon for cross-transport fields)
Env vars	upstream/claude-code-manifest.json knownEnvVars, docs/settings-reference.md env table, config/10-core.json env block
Hook wiring	config/40-hooks.json, src/hooks/, src/scripts/
Statusline	src/hooks/statusline.ts (Payload type)
Agent frontmatter	agents/*.md (currently uses tools, disallowedTools, maxTurns, permissionMode, effort, isolation, hooks, mcpServers, initialPrompt)
Slash commands	MANUAL.md "All Skills" table, skills/*/SKILL.md triggers
User-facing docs	MANUAL.md, CLAUDE-FULL.md, docs/settings-reference.md, docs/hooks-reference.md

Bucket each change as one of

• ADOPT — new upstream feature worth taking. List the exact files to edit.
• DEDUPE — native feature that now overlaps with cc-settings code. List the files/lines to delete. Look hardest for these — they're the cleanup wins.
• DOCS-ONLY — purely a documentation update (e.g. slash command renamed, table needs refresh).
• SKIP — not relevant (Windows-only, enterprise-only, fixes a bug we didn't have, etc.). Briefly say why.

Common DEDUPE patterns to look for

cc-settings has historically duplicated upstream work, then deleted it once the upstream version stabilized. Watch for these patterns:

• A new built-in hook event subsumes a custom hook script.
• A new tool replaces a wrapper we maintain (e.g. native Skill tool replaced our skill-activation.ts in v10.1.0).
• A new frontmatter field replaces a script-driven workaround.
• A new env var replaces a custom env-var dance.

Phase 4 — Stop. Present the plan.

Write a markdown table to the chat:

## v<A> → v<B> sync plan

### Adopt
| Change | Files | Notes |
|---|---|---|
| ... | ... | ... |

### Dedupe
| Native feature | What to remove | Why redundant |
|---|---|---|

### Docs-only
| Change | File |
|---|---|

### Skip
| Change | Reason |
|---|---|

Then ask the user one question: which rows do they approve?

• "Approve all" → continue with everything.
• "Approve subset" → user names rows.
• "Reject" → end the skill, no edits.

Do not edit before approval.

Phase 5 — Execute approved changes

For approved adoptions, edit the files directly. Schemas first (they're the contract), then config, then docs. For deduptions, delete the orphaned code and any tests that asserted on it.

After each schema edit, also update upstream/claude-code-manifest.json (knownSettingsKeys, knownHookTypes, knownEnvVars) — the scanner uses this as the source of truth.

Phase 6 — Manifest bump + version bump + CHANGELOG

upstream/claude-code-manifest.json
  - claudeCodeVersion: "<B>"
  - lastScan: <today ISO>
src/setup.ts
  - VERSION: bump (minor for new features, patch for fixes-only)
CHANGELOG.md
  - Prepend new section: "## [<new-version>] — <today YYYY-MM-DD>"

CHANGELOG entry structure (mirror prior entries — 10.1.0, 10.2.0, 10.2.1, 10.3.0 are good examples):

1. One-line summary.
2. Adopted: bullet per feature. State the upstream version, the file(s) touched, and a one-sentence "why this matters".
3. Deletions / Native-now-redundant: bullet per removed thing. State what replaced it and the upstream version.
4. Files changed: flat list, one per line.

Phase 7 — Validate

bun run typecheck
bun test
bun run upstream:scan   # should now show "no drift detected"
bun run compose | head  # spot-check that new fields surface in settings.json

If any fail: fix before moving on. Tests must pass.

Phase 8 — Commit + push

git add -A
git commit -m "feat(v<new-version>): sync with Claude Code v<B>

<one-paragraph summary>

Adopted:
- ...

Deletions:
- ..."
git push origin main

Use conventional commit prefix feat(v<X.Y.Z>): so the version stands out in git log. Do not push if anything in Phase 7 is failing.

What this skill does NOT do

• It does not edit user-installed ~/.claude/settings.json. cc-settings is the source — users get the changes by re-running setup.sh.
• It does not auto-open PRs. The upstream-sync GitHub Action handles manifest-only bumps; this skill is for the richer human-reviewed sync.
• It does not bump dependencies. That's a separate concern.

Mental model

cc-settings exists in three time zones:

1. Upstream — what Claude Code does today. Source: changelog + docs.
2. Manifest — what cc-settings believes upstream does. Source: upstream/claude-code-manifest.json.
3. Implementation — what cc-settings actually wires up. Source: schemas, config, hooks, agents.

Drift between (1) and (2) means the scanner is stale. Drift between (2) and (3) means our schemas accept things our installer never configures, or vice versa — usually fine, but worth flagging.

This skill aligns all three.