github-briefinglisted
Install: claude install-skill Skarlso/personal-workflow-skill
# GitHub Morning Briefing
Cross-repo attention triage for a maintainer. This is **not** code review. Never
assess whether a change is correct or should merge — only who is waiting, how
long, and what the next move is.
The scripts do all the fetching and arithmetic. You supply judgement: a headline,
a lede, and a short reason + next step for the items that matter. Everything you
write must trace to a line in the digest.
## Arguments
| User says | Pass |
|---|---|
| nothing | nothing — window is "since last briefing", 24h on first run |
| "last 3 days", "--hours 72" | `--hours 72` |
| an `owner/repo` | `--repo owner/repo` (repeatable) |
| "don't publish", "just here" | skip step 5 |
| "everything", "include watched repos" | `--full` |
## Step 1 — Collect
```bash
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/github-briefing/scripts/collect.py"
```
Writes `~/.claude/github-briefing/briefing.json` and updates
`~/.claude/github-briefing/state.json`. Takes ~10s. It prints the stats block.
Never pass `--no-state` on a real run: state.json is what makes "you have
ignored this 4 mornings running" possible.
This never marks anything as read. Notification state on GitHub is untouched.
## Step 2 — Read the digest
```bash
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/github-briefing/scripts/digest.py"
```
Read **only** this. `briefing.json` is ~200KB and must not enter context.
Field meanings, so you do not misread them:
- `OVERDUE` — waiting on you past the sta