athola/catchup
plugins/imbue/skills/catchup/SKILL.md
Summarizes recent git changes for context recovery after session breaks. Use when resuming work after a gap or handing off to another session.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market catchupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 4:42 AM158.7s4 files scanned
SKILL.md
- name:
- catchup
- description:
- Summarizes recent git changes for context recovery after session breaks. Use when resuming work after a gap or handing off to another session.
- alwaysApply:
- false
- category:
- analysis-methods
- - imbue:
- proof-of-work
- tools:
- []
- complexity:
- intermediate
- model_hint:
- fast
- estimated_tokens:
- 700
- progressive_loading:
- true
- module_strategy:
- context-based
- role:
- entrypoint
Table of Contents
- Overview
- When to Use
- Activation
- Progressive Loading
- 4-Step Methodology
- Output Format
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
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:proof-of-work, 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:proof-of-work for reproducibility, sanctum:git-workspace-review for git data. Feed to brainstorming or writing-plans as needed.
Token Conservation
Reference paths and 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
Related Skills
athola/friction-detector
tools
VerifiedTrustedCommunity
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
300SKILL.mdUpdated Apr 23, 2026
athola/validate-mr
testing
VerifiedTrustedCommunity
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
294SKILL.mdUpdated May 30, 2026
athola/palace-index-curator
development
VerifiedTrustedCommunity
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
294SKILL.mdUpdated May 30, 2026
athola/memory-clarity-probe
testing
VerifiedTrustedCommunity
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.
294SKILL.mdUpdated May 30, 2026