catchup
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.
npx skills add oliver-kriska/claude-elixir-phoenix --skill catchup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Catchup — Async-Team Return Briefing You've been away. This skill is a **thin orchestrator**: it resolves the window + sources here, then delegates the I/O fan-out, impact analysis, and brief assembly to the `catchup-runner` agent (Sonnet) so your (often Opus) session does not pay for summarization. You only print what the agent returns. ## Usage ``` /catchup # since you were last active /catchup --since "friday" /catchup --since "2h" --focus reviews-requested /catchup --since last-commit --depth deep /catchup --scope all # include cross-repo pings/reviews ``` Default is **repo-scoped**: every GitHub signal (reviews requested, notifications, mentions) is filtered to the repo you ran it in. Pass `--scope all` to also include cross-repo activity, which is then listed in its own separate section — never mixed into this repo's lists. ## Iron Laws 1. **Delegate the heavy work** — spawn `catchup-runner` (sonnet) for fan-out + assembly. Do NOT run the `gh`/`git` fan-out in this session; that defeats the cost/speed purpose. 2. **Resolve the window here, once** — the agent must never re-resolve it. Pass absolute `SINCE_*` values. 3. **MCP runs here, not in the agent** — Linear/Calendar MC
- Usage
- Iron Laws
- Workflow
- 1. Parse arguments
- 2. Resolve the time window (here, in this context)
- 3. Detect sources + pull MCP data (here)
- 4. Delegate to catchup-runner (Sonnet)
- 5. Present + stop
- Sources at MVP
- Graceful degradation contract
What does the catchup skill do?
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.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill catchup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.