菜单
Deterministic bi-directional sync between settings.local.json and settings.json. Local-only keys stay in local; all other keys are merged into both files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create/update the "deploy" branch with a clean project snapshot - strips all agent config (.agents/, .claude/, CLAUDE.md), draft-and-reference/, and malware-investigation/. Only project VBA files, docs, and README remain.
Find Claude memories written to the user-local app cache, compare with project memory, and merge them into .agents/memory/ (git-tracked). Run after sessions where memories may have been saved outside the project.
Explain every field shown in the project statusline (3-line layout) with concrete examples. Use when the user asks what a statusline field means, what ctx/5h/7d/dur/+N-N/style/think/effort/agent shows, or how the statusline is calculated.
Discover all available CLI tools on this machine and write their full paths to .agents/tools.local.json. Run once per machine or after installing new tools.
| file | ./.claude/skills/settings-sync/SKILL.md |
| name | settings-sync |
| description | Deterministic bi-directional sync between settings.local.json and settings.json. Local-only keys stay in local; all other keys are merged into both files. |
| scope | agent |
| updated-at | "2026-05-31T00:00:00.000Z" |
| allowed-tools | Read Edit Write |
Synchronize .claude/settings.local.json and .claude/settings.json so both files share
all common keys. Local-only keys remain in settings.local.json only and are never written
to settings.json.
These keys are rejected by Claude Code when present in the git-tracked settings.json.
They must live only in settings.local.json.
When merging: strip these keys from the settings.json output. Keep them in settings.local.json.
settings.local.json always wins on conflicts for shared keys.settings.json.Read .claude/settings.json and .claude/settings.local.json. If one does not exist, use the
existing file as source and create the missing file (omitting local-only keys if creating settings.json).
Classify keys into:
Highlight conflicts and local-only keys clearly. Wait for user confirmation before writing.
For settings.json: start with all keys, add missing shared keys from local (excluding local-only),
local overwrites on conflict, never include local-only keys.
For settings.local.json: start with all keys, add missing keys from shared, local overwrites.
Array merge rules (for permissions.allow / deny / ask): union + deduplicate, then:
Bash(mv *) covers Bash(mv "D:/some/path"). Remove redundant specifics.Tool(prefix *) and drop the specifics. Confirm before writing (wildcards widen scope).ask, never deny, unless the user explicitly says "deny".Hooks: merge by event name -> then by matcher; local overwrites on conflict.
Write both files. They will NOT be identical: settings.local.json has local-only keys that
settings.json does not. All shared keys must be identical after write.
Report: keys added (local->shared), keys added (shared->local), local-only keys kept, conflicts resolved, redundant entries removed, wildcards introduced, unchanged keys.