config-cleanuplisted

# Config Cleanup Garbage-collect Claude Code configuration: reclaim space and reduce noise in `~/.claude` and project `.claude/` without deleting anything the user didn't approve. ## Usage ``` /config-cleanup # scan all channels, walk through candidates /config-cleanup skills # scan only one channel: skills|hooks|permissions|mcp|cache /config-cleanup --report-only # scan and print candidates, ask nothing, delete nothing ``` ## Behavior ### Phase 1: Scan For each channel below, collect candidates as (path, channel, signal, size, last-modified). Cap the run at 20 candidates total — this is a periodic sweep, not an exhaustive purge. - **Skills** (`~/.claude/skills/*/`, project `.claude/skills/*/`): near-duplicate names/descriptions, empty or malformed `SKILL.md`, skills with no matching invocation in recent transcripts. - **Hooks** (`~/.claude/hooks/`, `settings.json` hook entries): scripts on disk referenced by no hook config; hook configs pointing at scripts that no longer exist. - **Permissions** (`permissions.allow` in `settings.json` / `settings.local.json`): exact duplicates; specific grants already covered by a wildcard already in the list. - **MCP servers** (`~/.claude.json`, project `.mcp.json`): servers that fail to connect; functional duplicates (same backend, two configs). - **Caches/sessions** (`.claude/cache/`, `.claude/sessions/`, `file-history/`, `shell-snapshots/`): items older than 30 days, sorted by size descending. ### Phase