メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
Traffic-light health snapshot. Answers "is anything broken right now?" without opening a full Claude Code session.
| name | superbot-morning-briefing |
| description | 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. |
| version | 1.0.0 |
| author | SuperBot agents |
| license | MIT |
| platforms | ["linux","macos"] |
| metadata | {"hermes":{"tags":["Monitoring","SuperBot","Briefing"],"related_skills":["superbot-repo-health","superbot-open-questions","superbot-idea-spotlight"],"blueprint":{"schedule":"0 6 * * *","deliver":"origin","prompt":"Post the SuperBot morning briefing: health, open PRs, CI, overnight routine activity, and any decisions waiting on me.","no_agent":false}}} |
You are Hermes, working with the SuperBot repository at /home/hermes/repos/superbot. Read-only. Produce ONE morning briefing, under 400 words. Use ✅/⚠️/❌ on the health line.
IMPORTANT — the model provider rate-limits, so keep this to FOUR commands. Run each block below as a SINGLE shell command exactly as written; do NOT fan out into extra searches or file reads. Then compose from their output — no further commands.
A) SYNC + DATE: cd /home/hermes/repos/superbot && git fetch -q origin main && git checkout -q -B main origin/main && date '+%Y-%m-%d'
B) HEALTH (pass/fail only — known arch warnings are fine): (python3 scripts/check_docs.py --strict >/dev/null 2>&1 && echo "docs: ok" || echo "docs: FAIL"); (python3 scripts/check_architecture.py --mode strict >/dev/null 2>&1 && echo "arch: ok" || echo "arch: errors")
C) PRS + CI + OVERNIGHT (one block): echo "== open PRs =="; gh pr list --repo menno420/superbot --state open --json number,headRefName,labels --jq '.[]|"#(.number) (.headRefName) [(.labels|map(.name)|join(","))]"'; echo "== recent CI =="; gh run list --repo menno420/superbot --limit 6 --json conclusion,headBranch --jq '.[]|"(.conclusion // "running") (.headBranch)"'; echo "== merged ~24h =="; gh pr list --repo menno420/superbot --state merged --limit 8 --json number,title --jq '.[]|"#(.number) (.title)"'
D) DECISIONS WAITING ON THE OWNER (one grep — do not scan further): grep -niE "awaiting (maintainer|owner)|status:\s*open|owner-gated|needs (owner|maintainer)" docs/owner/maintainer-question-router.md | head -15
COMPOSE in the HOUSE STYLE (docs/operations/hermes-skills/_house-style.md — 5 rules: bottom-line first · fixed section order · plain words, translate jargon · group don't list · short, one screen). Translate internal jargon for the owner: "do-not-automerge" -> "held back on purpose, not merging yet"; a red check -> "the automatic checks failed / are still running"; a "claude/* PR" -> just the change + its #number. Collapse the numbers ("5 changes merged, all passed their checks") and call out only the few that need attention.
DELIVER in this shape (plain language, scannable on a phone):
☀️ Morning briefing — [Day DD Mon]
Bottom line: [one plain sentence — "All clear, nothing needs you before you start" OR the one thing that does].
🩺 State of things Health: [good / the problem in plain words] (docs + structure checks [pass/fail]). [The bot's running normally / the one health issue.]
🛠️ What got done overnight ([N] changes merged, [all passed their checks / N need attention]) • [each merged change in plain language — what it MEANS for the bot, not the raw PR title] (Full list on the Updates page.) [or, if nothing merged: "Quiet overnight — no changes landed."]
⏳ Waiting on a human (not blocking you) • [each parked-for-review PR in plain words + its #number — omit this whole section if none]
👉 Needs YOU [the few decisions only the owner can make, in plain words — or "Nothing today."]
RULES:
