← ClaudeAtlas

archflow-doctorlisted

Use ONLY when the user asks for /archflow-doctor or "archflow doctor". Check the environment and project state — what Archflow needs, what is missing, and how to fix it
AZidan/archflow · ★ 27 · AI & Automation · score 81
Install: claude install-skill AZidan/archflow
> Arguments are the text after the skill name. # /archflow-doctor — Environment and project health check Arguments (`the text the user wrote after the skill name`): `--validate` also validates every `.archflow/` state file against its schema. `--fix` repairs the mechanical drift between this project and the installed plugin, and completes the project's `stack:` from what the repo declares. Empty → environment and project checks only. Report only, **except with `--fix`**, which is the one mode that writes. Without it, `doctor` never installs anything, never edits state, and never changes a phase. It ends with the exact commands the user can run themselves. ## How to read the results - **PASS** — present and usable. - **WARN** — absent or degraded, but Archflow still works. Say what it costs to leave it. - **FAIL** — Archflow cannot work correctly until it is fixed. Never upgrade a WARN to a FAIL because it would be nicer to have. codemap missing is a WARN. A v1.0 schema is a FAIL only for the commands that cannot run against it. ## Step 1 — Tooling Run each check, then report the table. Use `command -v` so a missing tool is a clean negative rather than an error. ```bash command -v git >/dev/null 2>&1 && git --version || echo "MISSING git" command -v node >/dev/null 2>&1 && node --version || echo "MISSING node" command -v python3 >/dev/null 2>&1 && python3 --version || echo "MISSING python3" command -v python3 >/dev/nul