commodore65

Audit and tune a Claude Code installation. Scans ~/.claude and ~/.claude.json for silently broken hooks, unused skills/plugins/MCP servers, stale memory files, orphan Claude/MCP processes, bloated telemetry, dead project entries, and contradictions in global or project CLAUDE.md. Produces a severity-ranked findings report with green/orange/red verdicts, then either auto-applies provably-safe cleanups, walks 12 audit phases interactively with per-phase approval, or runs read-only to produce only a report. Safety rails: file snapshots before any write, destructive ops always gated behind explicit approval, rollback commands generated on the fly. Trigger when the user says 'tune my claude code', 'audit claude setup', 'claude-tune', '/claude-tune', 'broken hooks', 'unused skills', 'orphan claude processes', or after terminal crashes left zombie sessions behind. Do NOT trigger for debugging project code (use health or investigate) or for creating new skills (use skill-creator).

Pressure-tests an implementation plan or spec — challenges scope in both directions, surfaces hidden failure modes, and recommends the strongest version of the plan. Use before building anything non-trivial, or when the user says 'pressure test this plan', 'stress test the scope', 'think bigger', 'rethink this', 'challenge this plan', or invokes /plan-pressure-test. Does NOT write or modify code.

Finds ghost state bugs: data computed but never persisted, state coupled across layers (memory/DB/API) but not synchronized, and values that silently reset or drift on process restart. Triggers on /ghost-audit or 'state audit' or 'persistence audit'.