forge-doctorlisted

# Forge Doctor Runs `scripts/doctor.py`, which performs 13 deterministic checks across environment, plugin integrity, project state, and global state. Each failing check includes a specific fix command. The script exits 0 if all checks pass (warnings allowed), 1 if any fail. ## When to Use - User types `/forge:doctor` or `/forge:health` - User says "Forge isn't working", "hooks aren't firing", "something's wrong with Forge" - User reports a Forge bug — run this BEFORE suggesting reinstall or workarounds - Pre-flight check before a Forge upgrade or before tagging a release - User asks "why isn't `/forge:init` running?" or any other Forge command-failure question - User pastes an error message that mentions Forge, hooks, or `pipeline/` ## Steps 1. Determine the project directory: - If `$ARGUMENTS` contains a path, use it - Otherwise use `${CLAUDE_PROJECT_DIR}` if set, else the current working directory 2. Run the diagnostic. Default invocation: ```bash python ${CLAUDE_PLUGIN_ROOT}/scripts/doctor.py --cwd "<project>" ``` 3. If the user wants only failures and warnings (no passes), add `--quiet` 4. If the user wants machine-readable output (parsing in a script), add `--json` 5. Present the output to the user **verbatim**. Do NOT paraphrase the `Fix:` lines — they are literal shell commands the user must run, not English advice 6. If the report shows recent entries under `Recent errors`, recommend the user view `.forge/hook-errors.log` for full tracebacks