跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

cc

Sync cc-settings with Claude Code and Codex upstreams, update a local install, or migrate a project's CLAUDE.md to AGENTS.md. Triggers "sync with claude code", "update cc-settings", "migrate to agents.md".

darkroomengineering · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add darkroomengineering/cc-settings --skill cc

技能说明


name: cc argument-hint: "[sync|update|migrate]" description: Sync cc-settings with Claude Code and Codex upstreams, update a local install, or migrate a project's CLAUDE.md to AGENTS.md. Triggers "sync with claude code", "update cc-settings", "migrate to agents.md".

cc — cc-settings management

Three-mode skill: sync keeps the repo current with the Claude Code and Codex CLI upstreams (maintainer task); update refreshes the active Claude Code, Codex, or combined local install (everyone); migrate moves a project's CLAUDE.md into AGENTS.md so every coding agent reads one file.

Mode: sync

Audit cc-settings against the Claude Code changelog and the Codex release notes; identify features to adopt and duplication to remove; stops for approval.

Track both upstreams and keep cc-settings (schemas, config, hooks, agents, docs, the Codex installer surfaces) 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 and upstream/codex-manifest.json against the live @openai/codex npm version. Each upstream has two outcomes:

  • No drift — manifest matches live. Nothing to sync for that upstream.
  • Drift detected — capture both versions. Format: manifest=A → live=B.

If neither drifts, tell the user "already in sync at Claude Code v, Codex v" and end. If only one drifts, run the remaining phases for that upstream alone and say so in the plan.

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.

Codex

Codex publishes release notes per GitHub release, not a changelog file. Stable releases are tagged rust-v<X>; alpha tags and Python SDK tags are not tracked. List the stable versions after the manifest version, then read each release body verbatim:

gh release list -R openai/codex --exclude-pre-releases --limit 20 \
  | grep -E '^[0-9]+\.[0-9]+\.[0-9]+\s' | awk '{print $1}'
gh release view rust-v<X> -R openai/codex --json body --jq '.body'

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):

BucketWhat to check
Settings keyssrc/schemas/settings.ts (zod schema, strict — drift fails parse)
Hook events / typessrc/schemas/hooks.ts (5-arm discriminated union as of v10.3.0)
MCP fieldssrc/schemas/mcp.ts (shared mcpCommon for cross-transport fields)
Env varsupstream/claude-code-manifest.json knownEnvVars, docs/settings-reference.md env table, config/10-core.json env block
Hook wiringconfig/40-hooks.json, src/hooks/, src/scripts/
Statuslinesrc/hooks/statusline.ts (Payload type)
Agent frontmatteragents/*.md (currently uses tools, disallowedTools, maxTurns, permissionMode, effort, isolation, hooks, mcpServers, initialPrompt)
Slash commandsMANUAL.md "All Skills" table, skills/*/SKILL.md triggers
User-facing docsMANUAL.md, CLAUDE-FULL.md, docs/settings-reference.md, docs/hooks-reference.md

For Codex changes, cross-reference these surfaces instead. There is no zod schema for any of them; upstream/codex-manifest.json knownConfigSurfaces lists what the installer writes or reads so a release note that names one is easy to spot.

BucketWhat to check
Native agents (agents/*.toml fields)src/lib/codex-native-agents.ts, codex/agents/
Command policy (rules/*.rules)codex/rules/darkroom.rules
Plugin manifest and hooksplugin.json, mcp.json, hooks/hooks.json (installed as $CODEX_HOME/hooks.json), src/lib/codex-runtime-manifests.ts
config.toml keys the installer readssrc/lib/codex-install-state.ts, src/lib/codex-skill-budget.ts
Skill loading and budgetssrc/lib/lint-skills.ts, docs/codex.md "skill descriptions were shortened"
Bridge (codex exec, codex review, model pins)src/lib/claude-bridge.ts, codex-run.ts, docs/codex-bridge.md
User-facing docsdocs/codex.md, codex/AGENTS.append.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
阅读完整来源 ↗