gw-doctor
Check that Galivelop-workflow is set up correctly in the current project and explain every failure with its fix. Use when something in the workflow misbehaves or after applying or updating it (run by
SKILL.mdskills/gw-doctor/SKILL.md
GitHubgw-doctor
If .claude/gw/gw-doctor.md exists in the project, read it first: it holds what is specific to the project.
The check itself is a script, doctor.py: deterministic, no AI, no network. This skill runs it, explains what it
prints and applies fixes the user approves. Reply in the project's language (.claude/gw.json).
Steps
Run it from the project root:
python3 .claude/gw/scripts/doctor.pyWithout a copy in the project (not applied yet), run the workflow's script on the project instead:
python3 <workflow>/scripts/doctor.py --root <project>.--jsongives the list as JSON.Read every line. Each is
OK,WARNorFAIL, followed byfix:with the command that repairs it. Exit code 1 means at least oneFAIL.Explain each non-OK line to the user in plain words: what is wrong, what it breaks in the workflow, and the fix.
docs/en/troubleshooting.md(thedoctor.pytable) says what each check means; read it when a line is not clear.Group the fixes by kind and offer them: commands that only change git settings or file modes (
git config core.hooksPath .githooks,chmod +x), commands that rewrite workflow files (/gw-update), and edits of project files (the log's next step,checkin.claude/gw.json,AGENTS.md).Apply only what the user approves. After a refused or interrupted call, run
git statusandgit diffbefore repeating it. Fixes touching.claude/settings.jsonor.githooks/may need the user's permission in Claude Code's auto mode.Run
doctor.pyagain and repeat steps 3 to 5 until noFAILis left. AWARNthe user chooses to keep is named in the final report, with the reason.
Cases that need care
hooks-pathWARN: another hook manager owns the hooks. Chain the workflow's hooks from it with the line the warning gives; never overwrite the manager's files or pointcore.hooksPathback without asking.check syntax-onlyWARN: abash -n/sh -ncheck command reads only its first file (several files, a glob or a substitution). Offer the one-command-per-file orforloop the warning gives; editcheckonly if the user agrees.check commandFAIL: the tool is missing or the command is wrong. Ask the user which; do not invent one.sessionWARN: the session was opened outside the repo. The fix is to reopen it from the repo, so tell the user; the script cannot do it.ci accessWARN: the agent cannot read the CI state of GitHub pushes. Installingghand logging in (gh auth login) or exporting a token is the user's call (credentials): tell them; never ask for or print the token.configFAIL: runpython3 .claude/gw/scripts/config.py validatefor the exact line; keys are indocs/en/config.md.
Report
Reply in 5 lines or fewer: the FAIL/WARN count before and after, what was fixed, what the user chose to leave,
and the next step.