agentleFS
eric-cieloeric-cielo/moflo/.claude/skills/healer/SKILL.md

healer

Skill19 starsChanged 3 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always include --json so output is machine-parseable.

    line 27
  2. Very specific:

    If --fix mode, read fixesApplied[] from the JSON payload and list {name, applied} per entry — applied=true → "fixed", applied=false → …

    line 33
  3. Very specific:

    If --install was passed, surface claudeCodeInstall.installed from the payload.

    line 34
  4. Very specific:

    If --kill-zombies was passed, surface zombieScan.killed / zombieScan.found from the payload.

    line 35
  5. Distinctive:

    Nudge based on what changed: Only mention next steps for state that *actually* changed:

    line 37
  6. Very specific:

    Don't: call flo doctor directly — use the healer alias for thematic consistency.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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:
    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 restarted → Statusline should refresh within ~5s.
    • moflo.yaml created → Review the new defaults at the project root before your next deep run.
    • Hook wiring repaired → Restart Claude Code so the new SessionStart hook fires next launch.
    • In audit-only mode with auto-fixable issues → Run /healer --fix to repair.

Rules

  • Don't re-document checks or fixes here. The CLI's --help and src/cli/commands/doctor-* are the source of truth.
  • Don't call flo doctor directly — use the healer alias for thematic consistency. They're equivalent CLI-side.
  • Don't swallow non-zero exit codes silently — surface them in the summary.
  • Note for users: Claude Code has its own built-in /doctor command that diagnoses Claude Code itself. This skill (/healer) diagnoses moflo, not Claude Code. The two are complementary, not duplicates. The healer rolls in the user-actionable parts of claude doctor (Claude Code version freshness vs npm latest) into its own Claude Code CLI check; the rest of claude doctor is a TUI on current releases and must be run interactively if you need its full report.

See Also

  • flo doctor --help — full flag/component list
  • /eldar — broader project-setup audit; consults the Healer as one input

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.