hermit-doctor

To diagnose a hermit installation, run the doctor checks to execute seven read-only health checks that validate configuration, hooks, state, cost, proposals, dependencies, and permissions. This generates a health report to ensure release readiness.

Running a health check on your hermit configuration involves executing the seven-point doctor diagnostic, which safely validates config, hooks, state, and permissions in read-only mode, writing a deterministic report to the state directory.

Yes, you can validate hermit hooks and permissions safely because the doctor diagnostic applies read-only validation with deterministic output. It surfaces configuration gaps and permission misconfigurations without altering the installation.

Suspicious behavior after deployment can be diagnosed by running the seven doctor health checks to surface state integrity problems, cost anomalies, and hook issues. The checks generate a report and log an auditing summary to isolate the problem.

The hermit doctor report gets saved to .claude-code-hermit/state/doctor-report.json, and a summary is appended to SHELL.md for traceability and auditing, providing a concise overview of the seven health checks.

No dependencies are required to run hermit diagnostics. The doctor checks operate independently to validate the installation's configuration, state, and permissions, producing a deterministic health report without external dependencies.