/doctor

A comprehensive health check of the local environment and remote configuration that surfaces every issue that could block a workshop participant or a fresh operator before they hit a real failure.

When to use it

Run this whenever something feels off and you want a fast triage, or as the standard “is this environment ready?” check before a workshop, demo, or fresh setup session. The command checks local tooling (gh CLI, git, Node, package managers), agent authentication (worker + reviewer accounts), hook installations, MCP server availability, and remote configuration (project board access, required workflows on main, branch protection). It reports each check as PASS / WARN / FAIL and produces a single overview the operator can act on.

Use it after running /bootstrap-workflow to confirm the activation worked. Use it before inviting a workshop attendee — they shouldn’t discover broken state on their own time. Use it when a different command unexpectedly fails — /doctor often surfaces the underlying config issue faster than debugging the failing command itself.

Don’t use it as a substitute for understanding why a specific command failed. /doctor is broad and shallow; for one specific failure, read the command’s pre-flight verification steps and check those directly.

How it fits

Reads the environment, produces a report, hands the operator a decision point. Pure observation — modifies no state.

What it does (quick)

• Runs scripts/doctor.sh for the local diagnostic battery
• Checks gh auth status for both worker and reviewer accounts
• Verifies project-board access works under the active account
• Confirms required workflows (agent-merge.yml, drain-merge-bridge.yml) exist on main
• Verifies hooks in .claude/hooks/ are executable and registered
• Reports MCP server availability
• Outputs PASS / WARN / FAIL per check with an actionable fix line for each failure

Related commands

• /upgrade — when /doctor shows the framework is out of date, run this to sync the latest files
• /bootstrap-workflow — /doctor is the right post-flight to confirm bootstrap-workflow’s activation took effect
• /sprint-status — the read-only sibling that observes board state (vs. /doctor’s environment focus)

Canonical spec: .claude/commands/doctor.md