harness-audit

Audits an existing coding-agent harness (CLAUDE.md, AGENTS.md, rules files, hooks, MCP and tool config, skills) against the project's past Claude Code sessions, then returns a ranked findings report plus proposed diffs applied only after approval. Flags bloated instruction files, rules with no evidence they help, prose rules nothing enforces, unused or overlapping tools, stale docs, and corrections that recur across sessions without a rule. Use when the user wants to prune, slim down, clean up or garden their agent setup, says CLAUDE.md has grown too long, asks which rules or MCP servers are dead weight, or says the agent keeps repeating mistakes without knowing which, even if they never say harness. Not for writing a new setup, rules, map sections or guardrails for a named problem area (use portable-harness), reviewing application code (use consistent-code-review), or tuning one skill's description (use tune-skill).