config-gc

Topics in the source

• Config GC — Garbage Collection for Claude Code Setups
• When to Activate
• Design Philosophy
• Scan Channels
• Workflow
• Example Scan Commands
• Anti-Patterns
• Best Practices

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. 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. 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 staleness signals — don't apply one rule everywhere. 4. Soft-delete first. Rename to .disabled > move to /.claude/gctrash/ > real deletion. Always keep an undo path. 5.

This is an excerpt. Refer to the complete source and its current requirements.