digest
One tight brief answering three questions: what moved recently, what is
waiting on the reader, and what is at risk of being forgotten. Lead with
what needs their attention, not with inventory.
1. Pick the scope
- If
$ARGUMENTS names a repo, a parent directory, or a focus area, use it.
- Else if the working directory is inside a git repo, digest that repo.
- Else find candidate repos one or two levels below the working directory
(directories containing
.git), and list what you found before digesting
more than a handful.
2. Collect — read-only, never mutate anything during a digest
- Per repo:
git worktree list plus git -C {dir} status --porcelain and
ahead/behind counts for each worktree — branch, clean or DIRTY, drift.
If the user has a multi-repo status helper on PATH, prefer it.
- Per repo with a GitHub remote:
gh pr list --state open (age, CI state,
review state) and gh pr list --state merged --limit 10 filtered to the
digest window (default: last 7 days). Note anything red or stuck.
- Per repo: the todo or state doc its
CLAUDE.md points at (e.g.
tasks/todo.md) — open gates, in-progress items, "awaiting owner"
markers. Plus git log --oneline --since='7 days ago' on the default
branch for what actually landed.
- Skip repos with no activity in the window rather than reporting silence.
3. Compose — decisions-first, one screen
Order by what the reader should act on, not by repo:
- Waiting on you — open gates, PRs awaiting review, unanswered
questions. Each with a one-line "what happens once you decide."
- Moved recently — merged PRs, closed gates, landed milestones; one
line each naming the decision it embodied, not the file list.
- In flight — active workstreams and where each stands; flag worktrees
that look abandoned (dirty with no commits in the window).
- Risks / drift — stale branches, red or stuck CI, worktrees ahead of
origin but unpushed, anything promised in a todo doc but untouched.
Omit empty categories rather than padding them. Keep the whole digest under
~40 lines. No disclaimers or footers.
4. Deliver
Print the digest directly in chat. If the invocation came from a scheduled
run whose instructions name another delivery channel, use that channel too.
Do not write files and do not commit anything.
1---2name: digest3description: Produce a cross-project status digest - a short, decisions-first brief synthesized from each repo's worktrees, branches, open PRs, CI state, and todo/state docs, ordered by what needs the reader's attention. Use whenever the user wants a status digest, weekly brief, Monday brief, standup summary, or cross-project status, says "digest", "weekly digest", "status brief", "what moved last week", or "where does everything stand", or when a scheduled digest run fires. Read-only - it never commits, writes files, or mutates any repo.4---56# digest78One tight brief answering three questions: what moved recently, what is9waiting on the reader, and what is at risk of being forgotten. Lead with10what needs their attention, not with inventory.1112## 1. Pick the scope1314- If `$ARGUMENTS` names a repo, a parent directory, or a focus area, use it.15- Else if the working directory is inside a git repo, digest that repo.16- Else find candidate repos one or two levels below the working directory17 (directories containing `.git`), and list what you found before digesting18 more than a handful.1920## 2. Collect — read-only, never mutate anything during a digest21221. Per repo: `git worktree list` plus `git -C {dir} status --porcelain` and23 ahead/behind counts for each worktree — branch, clean or DIRTY, drift.24 If the user has a multi-repo status helper on `PATH`, prefer it.252. Per repo with a GitHub remote: `gh pr list --state open` (age, CI state,26 review state) and `gh pr list --state merged --limit 10` filtered to the27 digest window (default: last 7 days). Note anything red or stuck.283. Per repo: the todo or state doc its `CLAUDE.md` points at (e.g.29 `tasks/todo.md`) — open gates, in-progress items, "awaiting owner"30 markers. Plus `git log --oneline --since='7 days ago'` on the default31 branch for what actually landed.324. Skip repos with no activity in the window rather than reporting silence.3334## 3. Compose — decisions-first, one screen3536Order by what the reader should act on, not by repo:37381. **Waiting on you** — open gates, PRs awaiting review, unanswered39 questions. Each with a one-line "what happens once you decide."402. **Moved recently** — merged PRs, closed gates, landed milestones; one41 line each naming the decision it embodied, not the file list.423. **In flight** — active workstreams and where each stands; flag worktrees43 that look abandoned (dirty with no commits in the window).444. **Risks / drift** — stale branches, red or stuck CI, worktrees ahead of45 origin but unpushed, anything promised in a todo doc but untouched.4647Omit empty categories rather than padding them. Keep the whole digest under48~40 lines. No disclaimers or footers.4950## 4. Deliver5152Print the digest directly in chat. If the invocation came from a scheduled53run whose instructions name another delivery channel, use that channel too.54Do not write files and do not commit anything.
jelbirt