claude-doctor-debugger

# Claude Doctor And Debugger Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise the absolute path of this plugin's root directory. Use this skill when Claude Code itself is failing or unclear: install/update state, auth, settings, hooks, plugins, MCP startup, keychain/API-key boundaries, safe-mode or bare-mode isolation, debug logs, auto-mode classifier behavior, IDE/Chrome integration, or native build installation. For broader safety contracts, read `$PLUGIN_ROOT/references/claude-cli-operation-contracts.md`. ## Inspect First Use the inspector and help output before running health checks: ```bash python3 "$PLUGIN_ROOT/scripts/claude_code_inspector.py" --commands doctor auto-mode install auth --json claude doctor --help ``` Avoid running `claude doctor` automatically in untrusted repositories because its help warns that it skips the workspace trust dialog and may spawn stdio servers from project MCP config. ## Isolation Lanes Use `--safe-mode` when customizations may be broken: ```bash claude --safe-mode claude --safe-mode --print "Check whether startup works." ``` Use `--bare` when the task needs minimal startup behavior, no keychain reads, no hooks, no plugin sync, no auto-memory, and no CLAUDE.md auto-discovery: ```bash claude --bare --print --settings /path/to/settings.json --add-...