/catchup
Context recovery after session breaks. Summarize recent git changes, extract key decisions, and identify pending work.
$ npx -y skills add athola/claude-night-market --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/catchup
Context preview
What this command does when you run it.
Context recovery after session breaks. Summarize recent git changes, extract key decisions, and identify pending work.
Command definition
catchup.mdname: catchup
description: Context recovery after session breaks. Summarize recent git changes, extract key decisions, and identify pending work.
usage: /catchup [baseline]
Catchup on Changes
Rapidly acquires context on recent changes using imbue's catchup methodology: confirm context, capture delta, extract insights, and record follow-ups.
Usage
# Catchup from last known state
/catchup
# Catchup from specific baseline
/catchup HEAD~10
# Catchup from date
/catchup --since "2 days ago"
What It Does
1. **Confirms Context**: Establishes current state and baseline for comparison 2. **Captures Delta**: Enumerates changes efficiently without deep-diving 3. **Extracts Insights**: Summarizes what changed and why it matters 4. **Records Follow-ups**: Identifies actionable next steps
Workflow
Baseline → Current → Delta → Insights → Follow-ups
↓ ↓ ↓ ↓ ↓
Known Target Changes Meaning Actions
state state list summary needed
Examples
/catchup
# Output:
# Catchup Summary
# ===============
# Scope: feature/payments branch
# Baseline: main (merge-base)
# Current: HEAD (15 commits ahead)
#
# Key Changes:
# - Payment processing overhaul (12 files)
# - New Stripe integration (3 files)
# - Test coverage additions (8 files)
#
# Follow-ups:
# - [ ] Review Stripe API key handling
# - [ ] Verify webhook endpoint security
/catchup --since "1 week ago"
# Week-based catchup with date filtering
Integration
Works with:
- `diff-analysis` - For semantic categorization
- `proof-of-work` - For reproducible context
- Git workspace commands for raw data
Output Format
## Summary
[2-3 sentence theme + risk overview]
## Key Changes
- [Item 1]: [what/why/implication]
- [Item 2]: [what/why/implication]
## Follow-ups
- [ ] [Concrete action with owner if known]
## Blockers/Questions
- [Item requiring resolution]
Token Conservation
- References file paths instead of reproducing content
- Summarizes rather than pasting large outputs
- Defers deep analysis to specialized skills
Read more
name: catchup description: Context recovery after session breaks. Summarize recent git changes, extract key decisions, and identify pending work. usage: /catchup [baseline]
Catchup on Changes
Rapidly acquires context on recent changes using imbue's catchup methodology: confirm context, capture delta, extract insights, and record follow-ups.
Usage
# Catchup from last known state /catchup # Catchup from specific baseline /catchup HEAD~10 # Catchup from date /catchup --since "2 days ago"
What It Does
1. **Confirms Context**: Establishes current state and baseline for comparison 2. **Captures Delta**: Enumerates changes efficiently without deep-diving 3. **Extracts Insights**: Summarizes what changed and why it matters 4. **Records Follow-ups**: Identifies actionable next steps
Workflow
Baseline → Current → Delta → Insights → Follow-ups ↓ ↓ ↓ ↓ ↓ Known Target Changes Meaning Actions state state list summary needed
Examples
/catchup # Output: # Catchup Summary # =============== # Scope: feature/payments branch # Baseline: main (merge-base) # Current: HEAD (15 commits ahead) # # Key Changes: # - Payment processing overhaul (12 files) # - New Stripe integration (3 files) # - Test coverage additions (8 files) # # Follow-ups: # - [ ] Review Stripe API key handling # - [ ] Verify webhook endpoint security /catchup --since "1 week ago" # Week-based catchup with date filtering
Integration
Works with:
- `diff-analysis` - For semantic categorization
- `proof-of-work` - For reproducible context
- Git workspace commands for raw data
Output Format
## Summary [2-3 sentence theme + risk overview] ## Key Changes - [Item 1]: [what/why/implication] - [Item 2]: [what/why/implication] ## Follow-ups - [ ] [Concrete action with owner if known] ## Blockers/Questions - [Item requiring resolution]
Token Conservation
- References file paths instead of reproducing content
- Summarizes rather than pasting large outputs
- Defers deep analysis to specialized skills
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Other commands on claude-night-market.
- /aggregate-logs
Generate LEARNINGS.md from skill execution logs.
Open command - /analyze-skill
Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.
Open command - /bulletproof-skill
Harden skills against rationalization and bypass behaviors
Open command - /context-report
Generate context optimization report for skill directories
Open command - /create-command
Create slash commands with brainstorming and best practices
Open command - /create-hook
Create hooks with brainstorming and security-first design
Open command

