catchup
Skill1 starsChanged 5 months agoMITView on GitHub
Re-orient after a break — read git state, the recent diff, and open TODO/FIXME markers, then restate in plain language what this branch is doing and the ONE next action. External working memory for when the thread was dropped. Trigger phrases "catch me up", "what was I doing", "where was I".
26 other projects use a version of this.
Adopted by
Most recently taken up by
- LilMGenius/paperthintheir own version, first seen Nov 15, 2026
- shortcuts/dotfilestheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 1, 2026
- Avijit07x/claude-dbtheir own version, first seen Oct 13, 2026
- poshan0126/dotclaudetheir own version, first seen Oct 8, 2026
Used with
Projects with it also use wrapup, plan and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Skeln-ioSkillwrapup
End-of-session closeout — commit, push, and optionally post a Slack summary. Use when you say "wrap up", "done for now", "save everything", or similar.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- LilMGenius/paperthin★ 1.4ksame name
- poshan0126/dotclaude★ 871same name
- getsentry/sentry-wizard★ 297same name
- Avijit07x/claude-db★ 233same name
- DeL-TaiseiOzaki/claude-code-orchestra★ 199same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- wilbeibi/catchup★ 81same name
- shortcuts/dotfiles★ 18same name
- blamechris/chroxy★ 8same name
- iopsystems/skills-mcp★ 6same name
16 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- claude-mdSkill
- context-budgetSkill
- db-querySkill
- debug-fixSkill
- eval-agentSkill
- explainSkill
- fix-issueSkill
- incident-ruleSkill
- pr-reviewSkill
- refactorSkill
- secrets-checkSkill
- setup-projectSkill
- shipSkill
- tddSkill
- test-writerSkill
- trace-agentSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If a PR exists for the branch: gh pr view for its state and checks.
- Distinctive: line 40
Do not open ten threads — surface the one that matters and offer to park the rest in the inbox.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
catchup
Trigger: "catch me up" / "what was I doing" / "where was I"
Standing rules: ../_conventions.md.
Eugen dropped this thread and is coming back cold. Your job is external working memory: reconstruct the state and hand back the ONE next step. Lead with the answer. Short and concrete — no wall of text, no ten open tabs.
Steps
- Read state (don't ask, look):
git branch --show-currentandgit log --oneline -5— branch + recent commits.git status -sandgit diff --stat— what's uncommitted right now.- Grep the diff and changed files for
TODO/FIXME/HACKmarkers. - If a PR exists for the branch:
gh pr viewfor its state and checks.
- Reconstruct the intent. From the branch name, commit messages, and the shape of the uncommitted diff, state in ONE sentence what this work is trying to do. If it's genuinely ambiguous, say "I can't tell from the code whether X or Y" — don't invent a narrative.
- Find the edge. Identify where work stopped: a half-finished function, a failing or pending test, a TODO, an unpushed commit. This is the re-entry point.
Report — this exact shape, nothing else unless asked:
- Branch:
<name>(<clean | N files uncommitted>) - Doing:
<one sentence> - Stopped at:
<the edge> - Next 5-min step:
<the single lowest-activation-energy action>
Do not open ten threads — surface the one that matters and offer to park the rest in the inbox.
- Branch:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

