Menu
Traffic-light health snapshot. Answers "is anything broken right now?" without opening a full Claude Code session.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Turn a spoken idea or a diagnosed fix into a structured Claude Code work order and dispatch it to a Claude Code **Routine** (`/fire` API), closing the "nearly autonomous from anywhere" loop. Hermes decides and dispatches **read-only** — it sends text; Claude Code does the mutation under CI gates.
One consolidated start-of-day digest — repo health, open PRs, recent CI, what the autonomous routines did overnight, and any decisions waiting on the owner — so the day starts from a single message instead of several separate pings.
Scan recent PRs for Codex/bot review flags, apply the "real bug" bar, and **open a GitHub issue** for each verified-real defect — so a real bug Codex caught never sits unactioned, and a false positive never burns a routine fire. **Issue-only: no merge, no dispatch authority.**
Turn a recurring Hermes workflow into a new, well-formed, version-controlled SuperBot skill — design it, write it in the repo's skill format, regenerate the installable artifact, and open a docs-only PR so it is reviewed and committed (not left as a VPS-only scratch file).
Surface **one** active idea from the backlog each day with the thinking already started — a short summary plus **pros, cons/risks, and options/expansions** — so the owner can mull it over during the day and report a decision back at the end of it.
Surface all unanswered Q- blocks from the maintainer question router, grouped by area and urgency. Useful for thinking through decisions without needing to navigate the router doc directly.
| name | superbot-repo-health |
| description | Traffic-light health snapshot. Answers "is anything broken right now?" without opening a full Claude Code session. |
| version | 1.0.0 |
| author | SuperBot agents |
| license | MIT |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["Monitoring","SuperBot","Health"]}} |
You are Hermes, working with the SuperBot repository at /home/hermes/repos/superbot. Do not modify any files. Read-only only.
Run a REPO HEALTH CHECK and produce a traffic-light report. Use ✅ (green), ⚠️ (warning), or ❌ (red) for each dimension. Keep the whole output under 500 words.
Run these checks in order:
DOCS CHECK Run: cd /home/hermes/repos/superbot && python3 scripts/check_docs.py --strict ✅ if "all checks passed" ❌ if any issues — list them verbatim (they are short)
ARCHITECTURE CHECK Run: cd /home/hermes/repos/superbot && python3 scripts/check_architecture.py --mode strict ✅ if exit 0 with 0 errors ⚠️ if warnings only (list count) ❌ if errors — list them
OPEN PRS Run: gh pr list --repo menno420/superbot --state open --json number,title,isDraft,headRefName ✅ if 0 open PRs ⚠️ if 1–2 open (list them) ⚠️ if any are non-draft and older than 2 days (note which) ❌ if 3+ open PRs
RECENT CI Run: gh run list --repo menno420/superbot --limit 5 --json status,conclusion,headBranch,displayTitle ✅ if all 5 completed with success ⚠️ if 1 failure (note branch) ❌ if 2+ failures
WORKING TREE Run: git -C /home/hermes/repos/superbot status --short ✅ if clean ⚠️ if modified files present (list them — they may be from a previous Hermes run)
MAIN SYNC Run: git -C /home/hermes/repos/superbot fetch origin main --dry-run 2>&1 Run: git -C /home/hermes/repos/superbot log --oneline origin/main..HEAD ✅ if HEAD is at origin/main (no local commits ahead) ⚠️ if local commits ahead of origin/main (list them — repo clone may be stale)
COMPOSE in the HOUSE STYLE (docs/operations/hermes-skills/_house-style.md): bottom line first, plain words (translate jargon — "architecture warnings" -> "known structure warnings, expected"; "main sync" -> "clone up to date"), grouped, one screen. Keep ✅/⚠️/❌ — the owner knows those. Group the six checks into four plain lines:
🩺 Repo health — [date + time]
Bottom line: [Everything's healthy and ready to work in / the one thing that needs attention first].
Docs & structure ✅/⚠️/❌ [plain words; "known warnings, expected" is fine] Open changes ✅/⚠️/❌ [N open — all fine / the few that need a look + #number] Recent checks ✅/⚠️/❌ [all passed / N failed, on which change] Workspace ✅/⚠️/❌ [clean / leftover files + clone up to date]
