メニュー
This skill should be used when the user says "show settings diff", "what changed in settings", "compare settings before after", "settings optimization preview", "preview settings changes", or "show me what tune-settings will change".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user says "check claude.md size", "is my claude.md too big", "claude.md token cost", "how big is claude.md", or when triggered automatically on session start to warn about oversized claude.md files.
This skill should be used when the user asks to "show recent changes", "show forge changelog", "show changelog for <project>", "what did I add this week", "what files did I touch today", "what packages keep recurring", "what drifts from the template", "review template suggestions", "show pending forge suggestions", "sync forge templates", "apply template suggestion", or "compute back-mapping suggestions". Provides read, drift-discovery, and template back-mapping workflows that wrap the `forge-db` MCP tools (`get_changelog`, `compute_suggestions`, `apply_suggestion`).
This skill should be used when the user says "build a wiki", "maintain a wiki", "ingest docs into wiki", "query my wiki", "set up llm wiki", "wiki-based knowledge base", "stop re-reading docs every session", "persistent knowledge base", or "compress my docs into wiki pages".
This skill should be used when the user says "auto compact", "enable auto compact", "compact on context full", "automatic context compression", "prevent context limit errors", "set up auto compaction", or "context keeps hitting limit".
Use this skill when the user says "/task_brain", "break down this task", "plan this", "decompose this problem", or when a task has multiple moving parts, unclear dependencies, or high ambiguity.
This skill should be used when the user asks to "add token counter to status line", "show context usage in status bar", "visualize token usage", "set up token status line", "live token counter", "show context window percentage", or wants to see token burn in the terminal status bar.
| name | Settings Diff |
| description | This skill should be used when the user says "show settings diff", "what changed in settings", "compare settings before after", "settings optimization preview", "preview settings changes", or "show me what tune-settings will change". |
| version | 1.0.0 |
Show a before/after diff of settings.json changes before applying. Always run this before writing settings changes.
Read all relevant settings files:
~/.claude/settings.json~/.claude/settings.local.json./.claude/settings.json./.claude/settings.local.jsonBased on optimization goals, compute the minimal diff needed. Never change settings not related to the stated goal.
Format diff clearly:
SETTINGS DIFF
═════════════
File: ~/.claude/settings.json
BEFORE AFTER
─────────────────────────────────────────────────────
"autoLoadMemory": true → "autoLoadMemory": false
"autoLoadSkills": true → "autoLoadSkills": false
[not present] → "compactOnContextFull": true
Impact:
Token reduction: ~[N] tokens per response (~[%]%)
Behavior change: Skills no longer auto-load. Use trigger phrases to load manually.
Reversible: Yes (edit settings.json to revert)
Always ask:
Apply these changes to [file]? (yes/no)
Never write without explicit confirmation.
When changes span multiple files:
SETTINGS DIFF — 2 files
═══════════════════════
[1/2] ~/.claude/settings.json
──────────────────────────────
"autoLoadMemory": true → false
+ "compactOnContextFull": true
[2/2] ./.claude/settings.local.json
──────────────────────────────────────
+ "plugins.autoEnable": false
Apply both changes? (yes/no/select)
After any settings change, show revert command:
To revert: edit [file] and restore original values.
Backup saved to: [file].backup.[timestamp]
Always create a .backup copy before writing changes.