I Built a Health Check CLI for Claude Code. My Setup Scored 63 on the First Run.

My Claude Code setup has been running autonomously for 200+ hours. I assumed it was solid. Then I built a diagnostic tool and ran it against my own config. 63/100. "Getting There." Turns out I had no context window monitoring. No activity logging. No error tracking from command output. Three blind spots I'd been living with for weeks. The Problem Claude Code's hook system is powerful but invisible. You configure it once in settings.json , maybe add a few CLAUDE.md rules, and forget about it. There's no way to know what you're missing until something breaks. I had a web-based scanner that asks 20 yes/no questions. It works, but you have to honestly answer each question yourself. That's the weak point — people overestimate their setup. The CLI Solution A CLI that actually reads your files and tells you what's there and what's not: npx cc-health-check (Or clone and run directly: node cli.mjs ) It scans: ~/.claude/settings.json — hook configurations CLAUDE.md files — rules and patterns Com