fusebase-flow-health-check

Solid

Use when the operator asks "is Fusebase Flow healthy", "check Fusebase Flow", "did fusebase update break anything", "Fusebase Flow status", "restore Fusebase Flow", or asks whether Fusebase CLI and Fusebase Flow agent files conflict. Runs the read-only health engine, reports layer verdicts (`HEALTHY`, `CLI_LAYER_DRIFT`, `CLI_VERSION_UNSUPPORTED`, `FLOW_LAYER_DRIFT`, `SHARED_MERGE_DRIFT`, `PARTIAL_UPGRADE`, `PUBLISHER_PACKAGING_DRIFT`, `EXCEPTION_IN_EFFECT`, `PARTIAL_UNVERIFIED`, `BROKEN`), and offers Flow recovery only when the drift is Flow-owned or shared-merge. For CLI-owned drift, instruct the operator to run the current FuseBase CLI refresh/update first, then Flow recovery.

AI & Automation 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Fusebase Flow Health Check ## Purpose Verify the local Fusebase Flow overlay and the shared FuseBase CLI / Flow agent surfaces without writing to the repository. The health engine now separates failures by ownership layer: | Verdict | Meaning | Recovery posture | |---|---|---| | `HEALTHY` | CLI-owned, Flow-owned, and shared-merge surfaces look intact AND every critical check ran clean. | No action. | | `CLI_LAYER_DRIFT` | CLI-owned assets are **missing** or structurally damaged. | Do not run Flow recovery first. Run the current FuseBase CLI refresh/update, then Flow recovery. | | `CLI_VERSION_UNSUPPORTED` | The installed FuseBase Apps CLI is **below the established incompatibility line**, so the CLI documents this Flow edition vendors are known-incompatible with it (`--app` resolution and command templates changed across the gap). The only CLI-version condition that changes the verdict. | Upgrade the CLI, then re-run. Flow recovery does not help — the mismatch is the CLI, not the overlay. | | `SHARED_MERGE_DRIFT` | Shared files are missing Flow overlay/merge additions. | Offer Flow recovery. | | `FLOW_LAYER_DRIFT` | Flow-owned mirrors or overlay files are missing/drifted. | Offer Flow recovery. | | `PARTIAL_UPGRADE` | Every real drift item is a stale DERIVED fact (adapter version/FR-range strings behind `VERSION`) — an upgrade that bumped `VERSION` and left the live strings behind. | Re-run `bash hooks/local/upgrade.sh` (or `sync-version-strings.sh`); the check RAN and f...

Details

Author
fusebase-dev
Repository
fusebase-dev/fusebase-flow
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Bundled in these plugins

fusebase-flow

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

flow-next-prime

Comprehensive codebase assessment for agent and production readiness. Classifies the project (lifecycle, topology, size, stack, shape), scans 8 pillars, verifies commands actually run, checks GitHub settings. Leads with a verdict + ranked next-actions; fixes agent readiness only. Triggers on /flow-next:prime.

701 Updated today
gmickel
AI & Automation Listed

sfh-flow-review

Audit an existing SimpleFlowHarness YAML flow for correctness, stability, convergence, recovery, security boundaries, portability, context/workspace use, external-tool identity, CI monitoring, and AI usability. Use when reviewing an AI-authored flow, diagnosing a brittle loop, checking a flow before release, or producing prioritized fixes without running paid or mutating steps.

0 Updated 1 weeks ago
Aero123421
Data & Documents Listed

doctor

Foundry health check (/foundry:doctor) — a thin, six-check probe (the v0.25.0 test-suite realignment shrank this from a 2,900-line drop-in-check registry to one file). Checks the plugin manifest loads, hooks.json parses with every referenced hook script present, every skills/*/SKILL.md frontmatter YAML-parses, the stack-profile lock (if any) resolves, the operator registry resolves, and the control-plane preflight (no dangling repos{} path, no ancestor manifest already governing this project dir). Plus four advisory-only lines never counted toward RED — permissions-policy, agent-teams, branches, and statusline (which names the first missing piece of the token-bar wiring). Fails CLOSED for an operator-invoked check (exit non-zero on any hard failure); the --session-start cadence is advisory (fail-open, never wedges a session). Trigger when the operator says "/foundry:doctor", "foundry health check", or to diagnose why a session looks unhealthy.

1 Updated today
lukasrepublic