hermit-doctor

Solid

Returns a twenty-four-check health report on the hermit installation (runtime, config, hooks, state-file integrity, cost, proposals, deps, version currency, permissions, docker, archival, reflect loop, scheduler, watchdog, context age, opus-wake spend, routine cost, heartbeat, routine monitor, raw storage size, sibling-plugin credential expiry, model pricing, channel liveness, context scan). Use when diagnosing an install, before a release, or after suspicious behavior. Activates on messages like "/hermit-doctor", "health check", "diagnose the hermit", "what's wrong", "run diagnostic".

AI & Automation 74 stars 15 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Hermit Doctor Runs twenty-four read-only health checks against the current hermit install (`channel-liveness` is the only one that performs outbound API calls — see Notes) and surfaces the summary. Safe to run at any time. Produces no side effects beyond writing `.claude-code-hermit/state/doctor-report.json` and appending a summary block to SHELL.md. ## Steps 1. Run the check script: ```bash bun ${CLAUDE_PLUGIN_ROOT}/scripts/doctor-check.ts .claude-code-hermit ``` The script writes `.claude-code-hermit/state/doctor-report.json` and prints the same JSON to stdout. It exits 0 unconditionally — on any internal failure the failing check reports `status: "fail"` in its own entry rather than crashing the report. 2. Parse the JSON. For each of the twenty-four checks in the report (`runtime`, `config`, `hooks`, `state`, `cost`, `proposals`, `dependencies`, `version-currency`, `permissions`, `docker-security`, `archive`, `reflect`, `scheduler`, `watchdog`, `context-age`, `opus-wake`, `routine-cost`, `heartbeat`, `routine-monitor`, `raw-size`, `credential-expiry`, `model-pricing-known`, `context-scan`, `channel-liveness`), emit one line using this format: - `✓ <id> — <detail>` when `status: ok` - `⚠ <id> — <detail>` when `status: warn` - `✗ <id> — <detail>` when `status: fail` 3. Append a summary section to `.claude-code-hermit/sessions/SHELL.md` under a new `## Doctor Report (<ts>)` heading. Use the same twenty-four lines from step 2. Place i...

Details

Author
gtapps
Repository
gtapps/claude-code-hermit
Created
6 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

doctor

Verify this repo's second-shift install/config state against the committed lockfile - never-installed, enabled-but-not-installed, version drift (behind AND ahead), project-scope records a user-scope one makes redundant, ref-less marketplace shadowing, skill/agent shadow collisions, opt-outs, config-lint. Prints exact remediation commands, scoped to the record that actually loads. Run after cloning, after upgrades, whenever the toolkit feels absent.

2 Updated today
manoldonev
Data & Documents Listed

doctor

Run a read-only hygiene + documentation audit on the current repo. TRIGGER when the user says "is this repo healthy", "check hygiene", "audit this repo" (when they mean inspect, not remediate), "what's drifted", "run doctor", "run a health check", "audit docs", "check for doc drift", "what's broken in this project", "are the hooks still installed", "/nyann:doctor". Do NOT trigger on "fix this repo" / "remediate" / "bring it into compliance" — those are retrofit (audit + fix). doctor reports, never writes. Do NOT trigger on "what does this repo do" (that's a docs pointer, not a hygiene audit).

6 Updated 1 weeks ago
thettwe
Data & Documents Listed

doctor

Foundry health check (/foundry:doctor) — a thin, six-check probe (the v0.25.0 test-suite realignment shrank this from a 2,900-line drop-in-check registry to one file). Checks the plugin manifest loads, hooks.json parses with every referenced hook script present, every skills/*/SKILL.md frontmatter YAML-parses, the stack-profile lock (if any) resolves, the operator registry resolves, and the control-plane preflight (no dangling repos{} path, no ancestor manifest already governing this project dir). Plus four advisory-only lines never counted toward RED — permissions-policy, agent-teams, branches, and statusline (which names the first missing piece of the token-bar wiring). Fails CLOSED for an operator-invoked check (exit non-zero on any hard failure); the --session-start cadence is advisory (fail-open, never wedges a session). Trigger when the operator says "/foundry:doctor", "foundry health check", or to diagnose why a session looks unhealthy.

1 Updated today
lukasrepublic