cc

# cc — cc-settings management Two-mode skill: **sync** keeps the repo current with Claude Code upstream (maintainer task); **update** refreshes the active Claude Code, Codex, or combined local install (everyone). Sync does not track a Codex upstream. ## Mode: sync Audit cc-settings against Claude Code changelog; identify features to adopt and duplication to remove; stops for approval. 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. ```bash 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 ```bash 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<X>" and end. - **Drift detected** — capture both versions. Format: `manifest=A → live=B`. ### Phase...