config-gc
Garbage collection for your Claude Code configuration. Periodically scans ~/.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/config-gc/SKILL.md
- License
- MIT
- Jobs
- Review, Guardrails, Context management
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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. ## 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. …