catchup
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.
npx skills add majiayu000/claude-skill-registry --skill catchup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
--- name: catchup description: | Triggers: follow-ups, catchup, insights, context-acquisition, summarization 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". category: analysis-methods tags: [summarization, context-acquisition, insights, follow-ups] dependencies: [imbue:evidence-logging] tools: [git, log-tools] usage_patterns: [context-catchup, handoff-preparation, progress-review] complexity: intermediate estimated_tokens: 700 progressive_loading: true module_strategy: context-based --- # Catchup Analysis Methodology ## Overview Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revis
- Overview
- When to Use
- Activation
- Progressive Loading
- Required TodoWrite Items
- 4-Step Methodology
- Step 1: Confirm Context
- Step 2: Capture Delta
- Step 3: Extract Insights
- Step 4: Record Follow-ups
- Output Format
- Integration
- Token Conservation
- Exit Criteria
What does the catchup skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill catchup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.