Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/session:catchupThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Rebuild full context of in-progress work. Use after switching context or starting a new session. ### Steps 1. Run the catchup script: 2. If the current branch matches `type/NNN-*`, fetch the full issue and recent comments: 3. Read changed files (from both committed and uncommitted changes in the catchup output). If more than 15 files, prioritize: - Source code over generated/lock files - Files mentioned in recent commit messages - Test files alongside their implementations 4. Present a concise summary: - **Branch:** name and commits ahead of default - **Linked ...
Rebuild full context of in-progress work. Use after switching context or starting a new session.
Run the catchup script:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/catchup
If the current branch matches type/NNN-*, fetch the full issue and recent comments:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/git-cli issue show <N>
Read changed files (from both committed and uncommitted changes in the catchup output). If more than 15 files, prioritize:
Present a concise summary:
npx claudepluginhub st0nefish/agent-toolkit --plugin session/catchupSummarizes recent git changes from a baseline, extracts key insights and decisions, and identifies pending follow-ups. Supports git refs or --since dates.
/catchupRestores project context after /clear by reading core docs like CLAUDE.md and memory-bank files, git status/logs/diffs, and sessions; outputs markdown summary of status, recent work, tasks, and next steps. Also supports deep/quick modes.