How do I install the Catchup skill?

Run npx skillmds add majiayu000/catchup-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Catchup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Catchup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Catchup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Catchup?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Catchup by majiayu000 — Agent Skill

Name: Catchup
Rating: 4.2 (5 reviews)
Author: majiayu000

Catchup

Methodology for summarizing changes, extracting insights, and identifying follow-up actions. Triggers: catchup, what changed, summarize changes, context acquisition, handoff, progress review, recent changes, git log analysis, sprint summary Use when: resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context DO NOT use when: doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead. Use this skill to quickly understand "what changed and what matters".

majiayu000 dc6d941 2 files · 4.0 KB Updated Sep 9, 2026 567 repo stars

File contents

Catchup Analysis Methodology

Overview

Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.

When to Use

Joining ongoing work or returning after absence
Before planning or reviewing handoffs
Any "what happened and what's next" context

Activation

Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"

Progressive Loading

Load modules based on context:

Git: Load modules/git-catchup-patterns.md for git commands. Consider sanctum:git-workspace-review for initial data gathering.

Documents/Notes: Load modules/document-analysis-patterns.md for meeting notes, sprint tracking, document revisions.

Logs/Events: Load modules/log-analysis-patterns.md for time-series and metric analysis.

Always Available: imbue:evidence-logging, TodoWrite workflow, structured output.

Required TodoWrite Items

catchup:context-confirmed - Boundaries established
catchup:delta-captured - Changes enumerated
catchup:insights-extracted - Themes identified
catchup:followups-recorded - Actions captured

4-Step Methodology

Step 1: Confirm Context

Define scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands.

Step 2: Capture Delta

Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies.

Step 3: Extract Insights

Per item: What (change), Why (motivation), Implications (tests/risks/deps). Rollup into themes.

Step 4: Record Follow-ups

Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly.

Output Format

## Summary
[2-3 sentence theme + risk overview]

## Key Changes
- [Item]: [what/why/implication]

## Follow-ups
- [ ] [Action with owner]

## Blockers/Questions
- [Item requiring resolution]

Integration

Use imbue:diff-analysis for risk assessment, imbue:evidence-logging for reproducibility, sanctum:git-workspace-review for git data. Feed to brainstorming or writing-plans as needed.

Token Conservation

Reference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading.

Exit Criteria

Four TodoWrite items completed
Context/delta/insights/follow-ups captured
Stakeholders understand state without re-reading sources

---name: catchup-3description: Methodology for summarizing changes, extracting insights, and identifying follow-up actions. Triggers: catchup, what changed, summarize changes, context acquisition, handoff, progress review, recent changes, git log analysis, sprint summary Use when: resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context DO NOT use when: doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead. Use this skill to quickly understand "what changed and what matters".--- # Catchup Analysis Methodology ## Overview Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently. ## When to Use - Joining ongoing work or returning after absence - Before planning or reviewing handoffs - Any "what happened and what's next" context ## Activation **Keywords**: catchup, summary, status, progress, context, handoff **Cues**: "get me up to speed", "current status", "summarize progress" ## Progressive Loading Load modules based on context: **Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering. **Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions. **Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis. **Always Available**: `imbue:evidence-logging`, TodoWrite workflow, structured output. ## Required TodoWrite Items 1. `catchup:context-confirmed` - Boundaries established 2. `catchup:delta-captured` - Changes enumerated 3. `catchup:insights-extracted` - Themes identified 4. `catchup:followups-recorded` - Actions captured ## 4-Step Methodology ### Step 1: Confirm Context Define scope (git branch, sprint, meetings), baseline (last state), and current target. See modules for commands. ### Step 2: Capture Delta Enumerate changed items with metrics. Prioritize source/config/docs over generated artifacts. See modules for strategies. ### Step 3: Extract Insights Per item: **What** (change), **Why** (motivation), **Implications** (tests/risks/deps). Rollup into themes. ### Step 4: Record Follow-ups Capture: Tests, Documentation, Reviews, Blockers, Questions. If none, state explicitly. ## Output Format ``` ## Summary [2-3 sentence theme + risk overview] ## Key Changes - [Item]: [what/why/implication] ## Follow-ups - [ ] [Action with owner] ## Blockers/Questions - [Item requiring resolution] ``` ## Integration Use `imbue:diff-analysis` for risk assessment, `imbue:evidence-logging` for reproducibility, `sanctum:git-workspace-review` for git data. Feed to `brainstorming` or `writing-plans` as needed. ## Token Conservation Reference paths + lines (don't reproduce). Summarize outputs. Defer deep analysis. Use progressive loading. ## Exit Criteria - Four TodoWrite items completed - Context/delta/insights/follow-ups captured - Stakeholders understand state without re-reading sources

Frequently asked questions