← ClaudeAtlas

doctorlisted

Validate framework configuration, check runtime dependencies, and report issues. Use when something isn't working or after setup.
joris887/exosuit · ★ 4 · AI & Automation · score 74
Install: claude install-skill joris887/exosuit
______________________________________________________________________ ## doctor Run a comprehensive health check on the framework configuration and project setup. ## 1. Command Verification Read CLAUDE.md Commands section. For each configured command (test, lint, format, build, typecheck): <IF condition="command is configured (not placeholder)"> Run the command in dry-run or check mode (e.g., `npm test --dry-run`, `ruff check --quiet .`). Report: PASS if it executes, FAIL if it errors, SKIP if not configured. </IF> <ELSE> Report: NOT CONFIGURED — suggest running `/bootstrap` to detect. </ELSE> ## 2. Hook Dependencies For each hook in `.claude/settings.json`: - Verify the hook script file exists and is executable - For `post-edit-format.sh`: check if at least one formatter is installed (prettier, biome, ruff, black, rustfmt, gofmt) - For shell hook scripts: verify git is available (used by stop.sh, session-start.sh) - Optional: check if jq is available (hooks fall back to sed without it) Report: PASS/WARN (missing optional tools)/FAIL (missing required tools) ## 3. Rule Relevance For each rule in `.claude/rules/`: - Read the YAML frontmatter `paths:` field - Check if any files in the project match those patterns - Report: ACTIVE (matches found) / DORMANT (no matches — rule will never trigger) - Check `docs/sessions/.activity-log.jsonl` for rule trigger frequency over the last 5 sessions - Rules that are ACTIVE but have zero trigger events in 5+ sessions: report as