agentleFS
Sign inStart free
Avijit07xAvijit07x/claude-db/skills/catchup/SKILL.md

catchup

Skill233 starsChanged 3 months agoApache-2.0View on GitHub

Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wrapup, explain and 4 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

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 4 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

    pr-review

    Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this from the project root:

    line 8
  2. Very specific:

    If the output is Nothing recorded for this project yet., say exactly that and stop.

    line 29
  3. Distinctive:

    Use only what the output shows.

    line 44
  4. Very specific:

    If there is no clear next step, write No clear next step found.

    line 46
  5. Distinctive:

    Do not save anything. Do not run any command that changes the repository.

    line 48

“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

Where did I stop?

Run this from the project root:

claude-db catchup

It prints what memory and git know about this project, in plain text. Some parts may be missing. A part with nothing in it is left out.

  • Last handoff is a note the user or a teammate saved on purpose. Trust it most, unless its heading says older than the last chat. Then the last chat is newer, and wins where they differ.
  • Not finished yet in another chat is a request another chat is still working on, or that was stopped. Say so under Open.
  • Last chat and Chat before are the other chats with the newest recorded requests, open or ended, newest first: the 5 newest requests in all.
  • Still to do are to-dos found in earlier chats.
  • Not committed yet is recorded work that no commit has covered.
  • Decisions and dead ends are what was chosen or ruled out, with the reason.
  • Branch says which branch you are on and how many files are uncommitted.
  • Git status and Recent commits are the live state of the repository.

If the output is Nothing recorded for this project yet., say exactly that and stop.

Answer in three groups

Reply with these three groups and nothing else. Keep each to a few short lines in plain words.

Done: what is finished. Take it from the last chat, the recent commits and the handoff's Done line.

Open: what is started but not finished. Take it from Not committed yet, Git status, the to-dos and the handoff's Open line.

Next: what to do first. Take it from the handoff's Next line, then from the to-dos.

Rules

  • Use only what the output shows. Do not read other files or search memory unless the user asks.
  • Mark anything you are unsure of with (guess). Never state a guess as a fact.
  • If there is no clear next step, write No clear next step found. Do not invent one.
  • Say how old the information is. Use the dates in the output, for example Last chat (Oct 6).
  • Do not save anything. Do not run any command that changes the repository.

Shipped with claude-db. It is replaced when claude-db updates.

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.

Reviews can't be read right now.

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.

Check your setup, free