← ClaudeAtlas

healerlisted

Run moflo's Healer (`flo healer`, alias for `flo doctor`) from inside the Claude session. Audit-only by default; pass `--fix` to apply auto-repairs, `-c <component>` for a single check. Use when something feels off (missing moflo.yaml, daemon dead, statusline empty, hooks not firing) or as a periodic health check. Distinct from Claude Code's built-in `/doctor`, which diagnoses Claude Code itself, not moflo.
eric-cielo/moflo · ★ 18 · AI & Automation · score 81
Install: claude install-skill eric-cielo/moflo
# /healer — moflo Installation Healer Thin wrapper around the `flo healer` CLI. All check + fix logic lives in the CLI; this skill just shells out, surfaces results in-thread, and gives one-line follow-up nudges. **Arguments:** $ARGUMENTS ## Procedure 1. **Memory first** (gate requirement): ``` mcp__moflo__memory_search { query: "doctor healer fix moflo.yaml gate hook wiring", namespace: "guidance" } ``` 2. **Run the CLI** with the user's arguments passed through: ```bash npx moflo healer --json $ARGUMENTS ``` - No args → audit-only. - `--fix` → CLI runs auto-repairs after the audit. - `-c <component>` → restricts to one check. - Always include `--json` so output is machine-parseable. 3. **Surface the JSON in-thread**. Group by status: - `✓ N passing` (count only) - `⚠ warnings` — list `name: message`; flag with `[auto-fixable]` when the result has a `fix` field - `✗ failures` — same - If `--fix` mode, read `fixesApplied[]` from the JSON payload and list `{name, applied}` per entry — applied=true → "fixed", applied=false → "needs manual action". The `results[]` array is post-fix state (re-evaluated), so report the final status. - If `--install` was passed, surface `claudeCodeInstall.installed` from the payload. - If `--kill-zombies` was passed, surface `zombieScan.killed` / `zombieScan.found` from the payload. 4. **Nudge based on what changed.** Only mention next steps for state that *actually* changed: - Daemon restar