Skip to content

oliver-kriska/claude-elixir-phoenix / plugins/catchup/skills/catchup

catchup

Verified

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

FileKindSize
SKILL.mdskill md6.0 KB
references/brief-format.mdmarkdown6.2 KB
references/config-schema.mdmarkdown3.2 KB
references/source-adapters.mdmarkdown9.3 KB
references/time-window.mdmarkdown7.6 KB

references/brief-format.md

View on GitHub
# Brief Format — Context Brief Framework, Catch-up Scoped

The output **is** the product. `/catchup` is not an aggregator that
dumps links; it produces a decision-ready brief in the discipline of
the 10-element Context Brief Framework (Intent, Audience, Scope In,
Scope Out, Deliverable, Constraints, Evidence, Acceptance, Risks &
assumptions, Timeline, Privacy). Each element is reinterpreted for a
*personal returning-to-work* brief below.

## Format constraint

Tight brief, not a novel. **Two screens, tops** for the file; the
inline summary is ~25 lines. Excerpts and one-liners — never raw
bodies. Ranked, not exhaustive. If it doesn't need *you*, it doesn't
go above the fold.

## Element mapping

| Framework element | Catch-up meaning |
|-------------------|------------------|
| Intent            | "You've been off N days. Do these first." + the 3-item ranked priority list |
| Audience          | Just you — your TZ, your role, your in-flight work |
| Scope In          | PRs/reviews/tickets/branches/meetings that touch *you* in the window |
| Scope Out         | Bot PRs, your own already-merged work, green CI, items needing nobody |
| Deliverable       | One markdown brief + a ≤25-line inline summary |
| Constraints       | Excerpt-only, prioritized, one file, honest about gaps |
| Evidence          | Links + one-line excerpts (PR #, ticket id, commit sha) — never thread dumps |
| Acceptance        | Reader knows what to do first and what the brief does *not* cover, in < 2 min |
| Impact on your work | Upstream changes that touch *your* in-flight files/areas — the differentiator, not just "what moved" |
| Risks/assumptions | Conflict risks ("unmerged migration may clash with your branch") + every skipped source |
| Timeline          | Window anchored to the user's local TZ (which Friday) + today's meetings in that TZ |
| Privacy           | No raw Slack/email/issue bodies off-device; v2 sources opt-in only |

## File template

```markdown
# Catch-up Brief — {Www, Mmm DD} ({SINCE_LABEL})

## Intent
You've been off {SINCE_LABEL}. Do these first:
1. {highest-priority action — usually a review requested of you, or red CI on your PR}
2. {second}
3. {third}

## Top priorities
| # | What | Why it needs you | Link |
|---|------|------------------|------|
| 1 | Review PR #1234 "…" | review-requested 2d ago, blocking {author} | {url} |
| 2 | CI red on your PR #1180 | {check} failed after merge of #1150 | {url} |
| 3 | PROJ-412 moved to In Review | assigned to you, awaiting your input | {url} |

## Impact on your work
_Upstream changes that touch files/areas you have in flight._
- ⚠ **Direct** — `lib/foo/bar.ex` changed by {sha}/PR #{n} ({ticket})
  and is also in your open PR #{mine} / branch `feat/foo`.
  {deep: one-line semantic note — what about your work it affects.}
- **Adjacent** — `{module}/` touched by {sha}; your `feat/foo` works
  in the same module — review before rebasing.
- _(or)_ No overlap with your in-flight scope this window.

## What moved (Scope In)
**GitHub** ({n} PRs, {m} pinged you) — _scoped to {repo}_
- #1150 "…" merged by @x — touches {area} ↔ PROJ-318
- @y commented on your #1180: "{≤1-line excerpt}"

**Other repos** _(only when `--scope all`; {q} cross-repo items)_
- {owner/other-repo} #42 review-requested of you 2d ago

**Git** (default branch +{k} commits by others)
- {sha} @x "{subject}"  ⚠ migration: priv/repo/migrations/…
- your branch `feat/foo` is {behind} behind origin/{def}

**Linear** ({source state})
- PROJ-412 → In Review (by @x){, or: "unverified refs (no MCP): PROJ-412, PROJ-571"}

**Calendar** ({source state})
- Missed: {meeting} (you were required)
- Today: 14:00 {meeting} — {TZ}

## Risks & assumptions
- Repo-scoped to {repo}; cross-repo pings/reviews not shown (run with `--scope all`).
- Unmerged migration in #1150 may conflict with your local `feat/foo`.
- Linear MCP absent — ticket signal is proxy-harvested, unverified.
- Window defaulted to 24h (no prior session found).

## Timeline
Anchored {SINCE_LABEL} → now (= {SINCE_ISO} absolute; all sources
compared on this instant — colleagues' other-TZ events included from
*your* boundary). Today ({TZ}): {meetings or "clear"}.

---
_Generated by /catchup. Excerpt-only; full threads not included._
```

## Inline summary (printed, not the file)

```
Catch-up: off {SINCE_LABEL}. {p} PRs, {r} reviews-requested, {c} commits by others{, linear/cal notes}.
Impact: {x} upstream changes touch your in-flight files{, or "none"}.
Do first:
  1. {action}  ({link})
  2. {action}  ({link})
  3. {action}  ({link})
Risks: {one-liner if any}.  Full brief → .claude/catchup/brief-{date}.md
```

## Depth knobs

- **quick** — Intent + Top priorities + counts + Impact (direct
  overlaps only, by filename). No Scope-In detail, no excerpts.
- **standard** (default) — full template above, one-line excerpts,
  Impact = direct + adjacent overlaps by filename.
- **deep** — + CI failure specifics, every PR↔ticket cross-link, and
  per-file *semantic* impact (read the incoming diff: what about your
  in-flight work it affects — schema, signature, behavior).

## Worked example (illustrative, generic)

> **Intent** — You've been off 3 days (since Fri May 13 00:00 CEST).
>
> 1. Review **PR #1093** "Account autocomplete component" — review
>    requested of you Sat, blocking @teammate.
> 2. Your **PR #1070** went red — `mix test` failed after #1106 merged.
> 3. **PROJ-916** moved to In Review, assigned to you.
>
> **Impact on your work**
>
> - ⚠ Direct — `lib/app/properties/survey.ex` changed by #1106
>   (PROJ-916) and is in your open PR #1070. The survey struct field
>   you read was renamed — your code won't compile after rebase.
> - Adjacent — `lib/app_web/live/navbar*` touched by #1070
>   (PROJ-449); your branch `feat/PROJ-880` works in the same LiveView.
>
> **Risks** — #1106 added `priv/repo/migrations/…_property_survey`
> on `main`; your `feat/PROJ-880` branch is 14 commits behind and has a
> migration of its own — rebase before generating a new one.
>
> **Linear** — unverified (no MCP this env): PROJ-412, PROJ-449,
> PROJ-755, PROJ-318 referenced in merges since Fri.

This is the bar: the reader spends two minutes, knows the first three
moves, and knows exactly what the brief did **not** see.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall