Catch Up
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Install
npx skills add petekp/claude-code-setup --skill catch-upgit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/catch-up ~/.claude/skills/catch-upPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Catch Up The person reading this has been away. While they were gone, agents (you and others) moved the project forward. They are juggling several projects like this one and do not read the code closely. Your job is to get them back in the driver's seat in under a minute: what changed, why it changed, and where their input would actually steer things. That framing decides everything below. They cannot act on a diff or a commit list, so do not give them one. They *can* act on plain ideas and clear choices, so give them those. ## What good looks like - **Plain English, zero jargon.** Every technical term either gets translated or explained the first time it appears. If a reader who has never seen the code would stumble on a word, rewrite it. See [Translating jargon](#translating-jargon). - **Altitude, not inventory.** Group changes by what they *mean*, not by file. One idea per bullet. The headline is the thing, not the line count. - **The why is the payload.** The diff says what changed; only the conversation says why. The reader steers on the why, so make sure it survives. - **Surfaces the forks.** The single most useful thing you can give a steerer is the list of decisions that are still open, or were made by default and could be reversed. That is where their attention belongs. - **Honest.** If something is half-done, untested, or went sideways, say so. A catch-up that hides loose ends makes steering worse, not better. ## How to do it
Details
- Skill name
catch-up- Repository
- petekp/claude-code-setup
- Path
skills/catch-up/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Catch Up skill do?
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
How do I install the Catch Up skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill catch-up. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Catch Up popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Deep Research
49petekp/claude-code-setup
Investigate a question that requires sustained research across sources and produce cited findings. Use for deep research requests; skip ordinary lookups and single-document reviews.
Clawhub
44iamclancyliang/nanobot-eino
Search and install agent skills from ClawHub, the public skill registry.
Timovi Dba
49theminimalcreator/timovi
DBA for the Timovi project. Designs and maintains the JSON state schema — state.json and feature.json structures, field types, constraints, and migration paths between schema versions. Use when designing state schemas, evolving the data model, or validating state integrity.
Herdr Names
49petekp/claude-code-setup
Rename Herdr tabs, panes, and agents so each sidebar entry says in a few words what that session is doing. Use whenever the user mentions Herdr and wants tab, pane, or agent names renamed, relabeled, cleaned up, tidied, or made clearer; says a tab or agent name is confusing, meaningless, stale, or just a number; asks what a tab is; or wants the sidebar readable at a glance, even if they only say 'fix the names' or 'label these'. Reads each pane's recent output and names the task, not the project and never the auto-generated terminal title. Needs to run inside Herdr (HERDR_ENV=1). Not for namin
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.