Restore context after /clear - summarize recent work and project state.
After clearing context with /clear, use this command to quickly rebuild understanding of:
- What was recently modified
- Current project state
- Outstanding TODOs and issues
- Where to resume work
# Recent commits (last 10)
git log --oneline -10
# Files modified in last 5 commits
git diff --stat HEAD~5 2>/dev/null || git diff --stat $(git rev-list --max-parents=0 HEAD)
# Current branch and status
git branch --show-current
git status --short# What changed today
git log --oneline --since="midnight" --author="$(git config user.name)" 2>/dev/null
# Uncommitted work
git diff --name-only
git diff --cached --name-only# Find outstanding work markers in recently modified files
git diff --name-only HEAD~5 2>/dev/null | head -20 | xargs grep -n "TODO\|FIXME\|XXX\|HACK" 2>/dev/null | head -30# Check for common state indicators
[ -f "package.json" ] && echo "📦 Node project: $(jq -r '.name // "unnamed"' package.json)"
[ -f "Cargo.toml" ] && echo "🦀 Rust project: $(grep '^name' Cargo.toml | head -1)"
[ -f "pyproject.toml" ] && echo "🐍 Python project"
[ -f "go.mod" ] && echo "🐹 Go project: $(head -1 go.mod | cut -d' ' -f2)"
# Active branch purpose (from branch name)
BRANCH=$(git branch --show-current)
echo "🌿 Branch: $BRANCH"Provide a structured summary:
Project: [name from package.json/Cargo.toml/etc] Branch: [current branch] Last Activity: [time of last commit]
- [commit message 1] - [files affected]
- [commit message 2] - [files affected] ...
- [list of modified files with brief description of changes]
- [file:line] TODO: [description]
- [file:line] FIXME: [description]
Based on recent activity:
- [Most likely next action based on patterns]
- [Alternative focus area]
After a long break:
/catchup
→ Full context restoration
Quick status check:
/catchup --brief
→ Just commits and uncommitted changes
Focus on specific area:
/catchup auth
→ Filter to auth-related changes
- Document before
/clear: Write a brief note in a commit message or CLAUDE.md before clearing context - Use with Memory Bank: Combine with
.claude/memory/files for persistent state - Branch naming: Use descriptive branch names (e.g.,
feat/user-auth) to aid context restoration
$ARGUMENTS