← ClaudeAtlas

healthlisted

Run when Claude feels off, ignores rules, or hooks/MCP need auditing.
woodiefernless68/claude-health · ★ 0 · AI & Automation · score 62
Install: claude install-skill woodiefernless68/claude-health
# Claude Code Configuration Health Audit Audit the current project's Claude Code setup with the six-layer framework: `CLAUDE.md → rules → skills → hooks → subagents → verifiers` The goal is to find violations and identify the misaligned layer, calibrated to project complexity. **Output language:** Check in order: (1) CLAUDE.md `## Communication` rule (global takes precedence over local); (2) language of the user's recent conversation messages; (3) default English. Apply the detected language to all output including progress lines, the report, and the stop-condition question. **IMPORTANT:** Before the first tool call, output a progress block in the output language: ``` Step 1/3: Collecting configuration data · CLAUDE.md (global + local) · rules/ · settings.local.json · hooks · MCP servers · skills inventory + security scan · conversation history (up to 3 recent sessions) ``` ## Step 0: Assess project tier Pick tier: | Tier | Signal | What's expected | |------|--------|-----------------| | **Simple** | <500 project files, 1 contributor, no CI | CLAUDE.md only; 0–1 skills; no rules/; hooks optional | | **Standard** | 500–5K project files, small team or CI present | CLAUDE.md + 1–2 rules files; 2–4 skills; basic hooks | | **Complex** | >5K project files, multi-contributor, multi-language, active CI | Full six-layer setup required | **Apply only the detected tier's requirements.** ## Step 1: Collect all data (single bash block) Run one block to collect data. ```