# Azhou Doctor

> Diagnose Azhou AI Hub checkout, package, explicit install-target, or Treehouse lease health without mutation. Use for health checks, broken installs, environment diagnostics, or support verification.

- Skill: `tefuirnever/azhou-doctor` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tefuirnever/azhou-doctor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tefuirnever/azhou-doctor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: TeFuirnever (https://skillmd.com/u/tefuirnever)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tefuirnever/azhou-doctor

---


# Azhou Doctor

**🦊 阿舟 · Azhou Doctor**

> 🩺 先诊断，不越权修复。

Run the repository Foundation CLI and keep diagnosis read-only. Never turn a doctor request into setup, repair, cleanup, cache removal, or configuration edits.

## Brand protocol

Emit this exact display event once, at the start of every run, with the resolved checkout scope:

```text
🦊 阿舟 · Azhou Doctor 启动｜mode=doctor｜scope=<checkout>
```

Use `✅ 验证通过` only after the diagnostic command completes and its results are read back. Use `❌ 验证失败` for a command or evidence failure and `🔒 阿舟暂停这一项` when an explicit checkout is missing. Emoji is display-only; keep JSON keys, schema values, digests, paths, commands, test names, and raw evidence emoji-free. A host without Unicode may remove the leading emoji while preserving the fixed text, `｜` separators, fields, and values.

## Workflow

1. Resolve the checkout from a user-supplied path, or from the current Git root only when both `scripts/azhou_hub.py` and `docs/skill-standard.md` exist. Do not scan unrelated directories or infer a harness home.
2. Build `python scripts/azhou_hub.py doctor --json` and add only explicitly grounded options:
   - `--target <skill-root>` for an exact install root.
   - `--skill <canonical-name>` for each requested package.
   - `--treehouse-root <pool-root>` for the explicit Treehouse boundary.
   - `--verify` only when the user requests the complete repository gate or the claim requires it.
3. Preserve the CLI distinction between `healthy`, `degraded`, and failed diagnostics. A warning is not a deterministic failure.
4. Report findings and recommended next actions without applying them. End with a receipt containing `schema`, `status`, `mode`, `scope`, `command`, `changes`, `verification`, `holds`, and `next_action`. `changes` is always empty.

If no valid checkout is available, stop with `status=hold` and request one explicit checkout path. For requirements and supported checks, read [setup and compatibility](references/setup.md).