config-gclisted

# Config GC — Garbage Collection for Claude Code Setups Borrowed from runtime garbage collection: periodically scan for objects that are no longer referenced, redundant, expired, or low-value, and reclaim the space. The critical difference: **here, collection requires a human in the loop. Never delete autonomously.** ## When to Activate - The user asks to clean up, audit, or slim down their Claude Code configuration - The user complains about too many skills, noisy hooks, or slow session startup - A monthly/periodic config review is due - After installing a large skill pack (e.g. this repo), to reconcile overlaps with existing setup Do NOT activate for: cleaning project source code (that's refactoring), clearing chat history, or uninstalling Claude Code itself. ## Active Config Root Derive one root at the start of the run and use it for every scan, backup, soft-delete, and log operation: ```bash ACTIVE_CONFIG_ROOT="${CLAUDE_CONFIG_DIR:-$HOME/.claude}" ``` Do not scan both the default and an override. When `CLAUDE_CONFIG_DIR` is set, it is the active root; otherwise use `$HOME/.claude`. ## Design Philosophy 1. **Append-only configs leak.** Skills, memory files, hooks, and permission entries only ever get added. Without periodic review they rot silently. 2. **Regular audits beat one-time purges.** Scan every ~30 days, propose a small batch of candidates each time. 3. **Per-channel strategies.** Each accumulation type (skills, hooks, permissions, ...) has its own stale