agentleFS
eugnmueller-87eugnmueller-87/claude-blueprint/.claude/skills/catchup/SKILL.md

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

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-ioSkill

    wrapup

    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

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 4 projects that use this

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
  1. Very specific:

    If a PR exists for the branch: gh pr view for its state and checks.

    line 23
  2. Distinctive:

    Do not open ten threads — surface the one that matters and offer to park the rest in the inbox.

    line 40

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read state (don't ask, look):
    • git branch --show-current and git log --oneline -5 — branch + recent commits.
    • git status -s and git diff --stat — what's uncommitted right now.
    • Grep the diff and changed files for TODO / FIXME / HACK markers.
    • If a PR exists for the branch: gh pr view for its state and checks.
  2. 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.
  3. 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.
  4. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.