doctor

Diagnose Hames plugin configuration and hook state in read-only mode.

5|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/baek-labs/hames --skill doctor-baek-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/baek-labs/hames/tree/main/packages/claude/skills/doctor
Command: npx skills add https://github.com/baek-labs/hames --skill doctor-baek-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Hames installation misbehaves, users cannot tell whether the cause is broken configuration, missing files, stale locks, or hooks that the host never executed. This Skill inspects the installation without changing anything and reports actionable recovery options. ## Core Features & Use Cases - Read-only diagnosis: Checks config parsing and schema, required .hames/ paths, entry boundary blocks, contract hashes, progress, review and knowledge linkage, evidence linkage, session ownership, the four bundled skills, and hook files. - Separated evidence: Distinguishes configured state, observed runtime behavior, and checks that have not been run, so a file's presence is never mistaken for host discovery or hook execution. - Safe recovery guidance: Shows each failed check's impact and only recovery actions the bundled runtime supports, requiring an explicit choice before changing a lock. - Use Case: After installing the Hames plugin, your indexes stop updating. Invoke /doctor to run the bundled runtime/doctor.js, see which checks failed, and get a supported recovery path without any files being modified. ## Quick Start Ask the agent to run /doctor against the current project root and report which configuration and hook checks failed.

Frequently Asked Questions about doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a broken Hames installation?▼

Invoke /doctor in a session at your project root. It runs the bundled runtime/doctor.js, checks config parsing, required .hames/ paths, contract hashes, and hook files, then reports failed checks with their impact and supported recovery actions.

Does the doctor command modify or repair my configuration?▼

No, the doctor check is strictly read-only. It never modifies, clears, recovers, or selects anything, and it requires an explicit recovery choice from you before any lock is changed.

Why does a hook file exist but never execute?▼

A file's presence does not prove host discovery or hook execution. The doctor report separates configured hook handlers, local execution observations, and unverified host trust so you can see which layer is failing.

What is the difference between /doctor and /index in Hames?▼

The /doctor command diagnoses configuration, recovery state, package wiring, and hook observations. The /index command owns inventory and file-rule auditing, so document placement and naming issues belong to /index.

What should I do if doctor reports an unconfigured root?▼

An unconfigured root means the folder was never set up as a Hames workspace. The doctor will offer /setup without changing any files, letting you configure folders and rules through the normal setup flow.