catchup
Scannednpx machina-cli add skill athola/claude-night-market/catchup --openclawTable of 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
When NOT To Use
- Doing detailed diff analysis - use diff-analysis instead
- Full code review needed
- use review-core instead
- Doing detailed diff analysis - use diff-analysis instead
- Full code review needed
- use review-core instead
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 establishedcatchup:delta-captured- Changes enumeratedcatchup:insights-extracted- Themes identifiedcatchup: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]
Verification: Run the command with --help flag to verify availability.
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
Troubleshooting
Common Issues
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag
Source
git clone https://github.com/athola/claude-night-market/blob/master/plugins/imbue/skills/catchup/SKILL.mdView on GitHub Overview
Catchup is a structured method to quickly understand recent changes across git history, meeting notes, sprint progress, and documents. It answers what changed and why it matters, helping you resume work after an absence or prepare handoffs. Do not use it for detailed diff analysis or full code reviews; use diff-analysis or review-core instead.
How This Skill Works
It loads context-specific modules (git, documents, logs) and follows a four-step method: confirm context, capture delta, extract insights, and record follow-ups. The result is a concise output in a defined format with a Summary, Key Changes, Follow-ups, and Blockers, suitable for sharing with stakeholders. It integrates with imbue:evidence-logging and related tooling for reproducibility.
When to Use It
- Joining ongoing work or returning after absence
- Preparing handoff documentation for teammates or stakeholders
- Reviewing sprint progress and project context
- Analyzing git history or documents to understand recent changes
- Clarifying what happened and what’s next in a project
Quick Start
- Step 1: Confirm context by defining scope, baseline, and target
- Step 2: Capture delta by enumerating changes and prioritizing sources
- Step 3: Output a structured report (Summary, Key Changes, Follow-ups, Blockers) and record TodoWrite items
Best Practices
- Define the scope, baseline, and current target up front
- Capture deltas by enumerating changes and prioritizing sources over generated artifacts
- For each item, note what changed, why it happened, and implications for tests or dependencies
- Roll up insights into themes and highlight risks or blockers
- Record follow-ups as actionable TodoWrite items with owners and next steps
Example Use Cases
- A developer returning from PTO to catch up on commits, notes, and tasks
- A lead preparing handoff documentation for a new on-call engineer
- A Scrum Master reviewing sprint progress for stakeholder updates
- A maintainer analyzing git history to understand changes and risks
- A team summarizing meeting notes and system logs to define next steps
