Skip to content
Filip Stack
Documentation: catch-up

catch-up

Recaps a thread's goal, progress, and next step in four lines when you return to it.

Install
On its own
Runs
Manual · /catch-up
Source
SKILL.md
npx skills add filipgutica/filip-stack -g -a claude-code codex -s catch-up -y

What it does

Catch-up answers from the conversation alone, so it returns in seconds and runs no commands. It reminds you what the thread is for and where it stands. It does not re-verify the repository.

When to use it

Install the skill with the command above. Catch-up runs only when you invoke it: /catch-up in Claude or $catch-up in Codex. Use it when you return to a thread and have lost track of it.

For verified branch state and check results before a handoff, use checkpoint instead.

How it works

The agent reads the conversation and writes the recap without running tools. It names PRs, files, and threads as links when the conversation has them, and marks claims the conversation never verified. When you ask for verified state or a handoff, it recommends checkpoint instead of a recap.

SKILL.md has the exact format.

What you get

Four lines:

  • Goal: what the thread is for.
  • Done: what it has reached so far.
  • Now: what is in progress or waiting, or that the thread can close.
  • Next: the next step and who owns it.
  • checkpoint

    Captures current work, evidence, and next actions for a pause or handoff.

    Standalone