← ClaudeAtlas

baton-doctorlisted

Check that Baton's hooks actually run on this machine, not only that Baton is installed - shows when each hook last finished, or that it crashed. Use when the human asks whether Baton is working, when the session-start board did not appear, or after installing or updating Baton.
StanimirTenev/baton · ★ 0 · AI & Automation · score 72
Install: claude install-skill StanimirTenev/baton
# Baton doctor — installed is not running A plugin can be installed and enabled and still never run: no Python 3.8+, or on Windows no Git for Windows (the hooks start through Git Bash). Nothing on the screen says so. Since v3.12.0 every hook leaves a heartbeat (since v3.20.0 when it finishes, and a crash marker when it raises; since v3.21.0 a start mark, so a run killed from outside shows); this reads them. It reads only and sends nothing. Output in the human's language. Commands and hook names stay as they are. ## Run it Installed as a plugin (Claude Code fills in both paths): ``` CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" BATON_SESSION="${CLAUDE_SESSION_ID}" python3 "${CLAUDE_PLUGIN_ROOT}/tools/baton_doctor.py" ``` If the line above still shows the literal text `${CLAUDE_PLUGIN_ROOT}`, this is a script install: run `BATON_SESSION="${CLAUDE_SESSION_ID}" python3 <repo>/tools/baton_doctor.py`, where `<repo>` is `repo` in `~/.claude/baton/hooks/baton.local.json`. On Windows use `python` for `python3`. If Python answers "can't open file", the source Baton was installed from is gone from that path: tell the human the clone was moved or removed (the hooks still run; the tools do not), and that cloning it back to that path, or installing again from a new clone, brings the tools back. `BATON_SESSION` is this session, whose turn is not over yet: the doctor leaves it out of the turn check below. ## Read it to the human - **🔴 ALL HOOKS ARE SWITCHED OFF** (since v3.23.0) — `"di