Claude Tune

claude-tune


**Audit and tune your Claude Code setup** — hooks, skills, plugins, MCPs, memory, processes, disk.

Safety-railed, three modes, snapshot-and-rollback on every mutation.

---

What it does

claude-tune is a Claude Code skill that walks your installation through 12 audit phases and surfaces:

• 🔴 Silently broken hooks — scripts the harness "runs" but that exit early because they rely on removed env vars from Claude Code 1.x
• 🟠 Unused skills, plugins, MCP servers, and agents — categorized HEAVY / ACTIVE / COLD / DEAD with a session-log observation window
• 🟠 Stale memory files — dead references, filename/content mismatches, past-due dates
• 🔴 Orphan Claude/MCP processes — left behind by crashed terminals, classified as "mine vs orphan"
• 🟢 Disk cruft in ~/.claude/ — telemetry failed-batch buildups, old claude-tune backups
• 🔴 Dead project entries in ~/.claude.json — paths that no longer exist on disk
• 🟠 Contradictions in global or project CLAUDE.md — narrow generalizations, static lists inside dynamic-discovery blocks
• 🟠 Bloated MCP servers — globally-scoped but rarely used; proposes an on-demand loading pattern

For each finding it produces a severity-ranked table and, if you approve, applies provably-safe cleanups. Every mutation emits a `ROLLBACK:` command alongside.

---

Install

git clone https://github.com/commodore65/claude-tune ~/.claude/skills/claude-tune

Open a new Claude Code session and say one of:

• claude-tune
• audit my claude code
• tune claude code
• clean up claude setup
• broken hooks
• unused skills
• orphan claude processes

The first thing the skill does is ask which mode to run.

---

Three modes

| Mode | Description | When to use | | ---------