Morning Brief
Executive morning briefing: overnight status across key systems, recent activity, alerts, and priorities — delivered as a single actionable summary.
How It Works
- Start of day: /morning-brief — situational awareness in under two minutes
- Gather data in parallel: System health · overnight commits · open PRs · CI runs
- Verify live processes: ps / docker ps — absence of errors is not proof of health
- Synthesize the signal: Notable changes, alerts, and PRs needing action
- Single executive brief: Status · activity · alerts · PRs · today's top 3 priorities
Invocation Triggers
/morning-briefmorning briefdaily briefwhat happened overnightcatch me upUse Cases
- Start the day with a consolidated status across all your systems
- Get an overnight summary after coming back to the machine
- Prioritize the day based on what needs immediate attention
The Problem
You start the day blind. Something deployed overnight, a process died at 3am, two PRs are waiting on you, and a CI run went red — and you find out about each one at the worst possible moment, one tab at a time. Reconstructing what happened means a dozen commands across a dozen repos before you have even decided what matters. By the time you have the picture, half the morning is gone and you still have not started the actual work.
What It Does
- 1Check live system health
Runs a real process check with ps aux or docker ps — never inferring health from log silence, because a dead process logs nothing. Pulls recent error lines and checks disk and memory.
- 2Pull overnight git activity
Loops every repo in the Dev directory and lists everything committed in the last 24 hours, repo by repo. The brief reflects actual git state, not recalled state.
- 3List open PRs and CI status
Runs gh pr list for everything waiting on review with its age, and gh run list for the actual conclusion of the latest CI runs — not a guess that they are probably passing.
- 4Synthesize the brief
Assembles all six sections — Status, Overnight Activity, Alerts, Open PRs, Today's Priorities — into one document. Empty sections are written explicitly, so a clean result never looks like a skip.
- 5Derive the top three priorities
Reads its own gathered data and ranks the three things that actually need attention today. This is the actionable output — a status report without next actions is information, not intelligence.
What You Get / What It Doesn't Do
- One brief with all six sections, none omitted
- System health confirmed by a live process check, not log absence
- An overnight git activity list pulled per repo
- Open PRs with age, and CI runs with their real conclusion
- A ranked top three derived from the actual data
- Summarize overnight activity from memory instead of running the commands
- Call systems nominal because no error was logged
- Act on the priorities — it surfaces them, you decide
- Skip a section because it is empty — it writes the zero explicitly
Tips
A nominal status from log silence is a lie. A dead process logs nothing. Health means ps aux or docker ps confirmed the thing is actually running.
Open PRs: 0 is information. A missing section looks like the skill skipped it. Always write the zero so a clean morning reads as clean, not incomplete.
Status without a next-action list is just data. If the brief stops before the top three, it failed — the ranking is the intelligence you actually came for.
Get the Skill
Unlock the full Morning Brief SKILL.md — drop it into ~/.claude/skills/ and trigger it by name.
- One brief with all six sections, none omitted
- System health confirmed by a live process check, not log absence
- An overnight git activity list pulled per repo
- Open PRs with age, and CI runs with their real conclusion
Commonly Used With
29 more production skills ready to install.