bridge-health

Solid

Quick health check on the bridge daemon (CEO machine + any exec mirrors). Surfaces heartbeat staleness, version drift, active sessions, and the Phase 1 -> Phase 2 adoption gate metrics. Use when the dashboard feels stale, the sync-pill is red, the daemon may have crashed, or before a /push-updates that changes daemon config. NEVER auto-trigger - invoke explicitly via /bridge-health.

AI & Automation 10 stars 1 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
35
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Bridge daemon health check Wraps two CLI scripts into a single CEO ops command: - `scripts/daemon-fleet-health.py` -- fleet status grid (heartbeat freshness, version drift, active session count per workspace) - `scripts/bridge-daemon.py --health` -- live `/health` endpoint probe on the local daemon Optionally surfaces the adoption-gate metrics (Phase 1 -> Phase 2 gate from the bridge spec, section 4) when called with `--gate`. ## When to use - Sync-pill on the dashboard is amber or red - /push-updates pushed a daemon config change and the CEO wants to verify the fleet picked it up - The dashboard feels stale and you don't know if the daemon is dead or just slow - Before deciding whether to scale from Phase 1 (CEO only) to Phase 2 (full CEO coverage) or Phase 3 (exec pilot) — `--gate` shows the gate verdict ## When NOT to use - Single-script debugging: prefer `python scripts/bridge-daemon.py --health` directly when the question is "is this daemon process alive on this machine right now". /bridge-health is for the rollup. - One-line grep summary: prefer `python scripts/bridge-daemon.py --status` for a single grep-friendly line (port + pid + uptime + version + config_v + sessions + errors + last_hb). Designed for cron + shell pipelines. - Triggering refresh: use the dashboard's sync-pill (top right) instead. - Tweaking config: edit `corporate/daemon/config.yaml`, commit, run /push-updates. /bridge-health is read-only. ## Arguments | flag | default...

Details

Author
mishahanin
Repository
mishahanin/heading-os
Created
4 weeks ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Anthropic · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ainb-fleetdaemons

Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a pid-recycle. Use this when you need to answer "are my background daemons actually alive?" — not just installed, but serving. Default output: a fixed-width text table. Pass --format json for tooling.

18 Updated today
stevengonsalvez
Data & Documents Listed

gabe-health

Codebase health analysis — god files, churn hotspots, coupling clusters, bug concentration, and scope creep vs plan. Run before epics, during retros, or when things feel fragile. Usage: /gabe-health [focus]

0 Updated 3 days ago
khujta
Data & Documents Listed

health-check

Run a full self-diagnostic of the Forge plugin — executes hook unit tests, checks lesson-store integrity, and reports overall status as healthy, degraded, or failing. Use when the user types `/forge:health-check`, asks "is forge healthy?", "check the plugin health", "run the health check", or "are the hooks working?". Never silently disables hooks — any auto-disable action requires explicit opt-in via the `health.auto_disable_hooks` config flag in .forge/config.yaml and is always surfaced to events.jsonl and health-surface.txt.

0 Updated today
tonmoy007