Ccinspect

---

Goal of the project

Provide Claude Code users with full visibility and confidence that their configuration is correct, conflict-free, efficient, and behaving as intended — like a linter + debugger for your Claude Code setup.

The problem it solves

Claude Code has a complex, layered configuration system — settings files, CLAUDE.md memory files, rules, agents, skills, commands, MCP servers, hooks, and plugins — spread across multiple locations with precedence-based merging. As projects grow, it becomes hard to:

• Know what's actually in effect after all layers merge
• Spot contradictions between levels (e.g., allow at user level, deny at project level)
• Detect dead config (rules with globs matching nothing, orphan agents)
• Understand token budget impact (how much context is consumed at startup)
• Verify that configuration behaves as intended at runtime

Claude Code uses **30+ config files** across **7+ locations** — and when they conflict, debugging is painful.

**ccinspect** fixes that with next capabilities:

🔍 **Discover** — finds every config file across all scopes and shows sizes, tokens, git status 🧹 **Lint** — runs 52 rules catching security gaps, dead references, conflicts, and bloat 📋 **Evidence** — see exactly which lines triggered each detection 🔗 **Blame** — shows the effecti