config-managerlisted
Install: claude install-skill shimosan/claude-code-save-chat
# config-manager
Thin Codex entrypoint for the library config workflow.
## Source Of Truth
For any review/apply/config-policy task, read and follow:
1. `<library_path>/scripts/config-update.md`
2. Only when that workflow tells you to: `<library_path>/scripts/config-apply-recipes.md`
3. Only when the user asks to run or inspect patch recipes: `<library_path>/scripts/config-apply-patches.md`
Do not duplicate policy, private recipes, or apply rules in this skill.
## Resolve `<library_path>`
Use the current workspace if it contains `scripts/config-update.md`.
If not, read `library_path` from the host-info section of `~/.claude/CLAUDE.md` (or, on machines not yet migrated to the unified layout, from `~/.claude/CLAUDE.local.md`). If neither defines `library_path`, ask the user. Do not invent paths.
## Invocation
Trigger for requests such as:
- `config-manager`
- `設定の差分を見て`
- `最近の config 変更を見せて`
- `<machine> の設定をこの端末に取り込みたい`
- `この設定を前の状態に戻して`
- `config policy に記録して`
- `helper の出力をそのまま見せて`
- `生の timeline / drift / nway / list を見たい`
## Behavior
- For review/apply/config-policy work, read `scripts/config-update.md` first and follow it.
- For patch recipe requests, read `scripts/config-apply-patches.md`; keep the detailed behavior in the script-specific docs and get explicit approval before any live change.
- For pure overview requests, you may directly run `scripts/config-log-helper.py timeline`, `drift`, or `nway`; if interpretation, proposal, policy updates, or apply wor