ketchup
FeaturedEaster-egg alias for /catchup. Same return-from-absence briefing, squeezier name. Use exactly like /catchup — all flags pass through unchanged.
Install
Quality Score: 95/100
Skill Content
Details
- Author
- oliver-kriska
- Repository
- oliver-kriska/claude-elixir-phoenix
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
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.
catchup
Reads every comment, review, inline review thread, and state change on one GitHub repo's issues and PRs since the user last participated, then reports what is waiting on them, what is waiting on someone else, and what needs nothing. Read-only; never merges, comments, labels, or closes. Use when the user returns to a repo after time away, or before they resume work on an issue or PR — phrasings like "catch me up on <repo>", "did anything change", "is anyone waiting on me", "what did I miss", "any new comments", "sitrep on <repo>", "re-read the threads before I start". Accepts a bare repo name and resolves it against the local clone, so repos owned by a collaborator work.
catch-me-up
Use for "catch me up", getting oriented in an unfamiliar repo, or returning after time away: module map and entry points, repo conventions, test structure, unfamiliar syntax, or what changed recently. Six exploration modes with deliberately visual output. Routes feature traces to how and decision rationale to why.