Restore context after /clear by summarizing recent work and project state
60
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./examples/skills/catchup/SKILL.mdRestore context after /clear - summarize recent work and project state.
After clearing context with /clear, use this command to quickly rebuild understanding of:
# 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]
Based on recent activity:
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
/clear: Write a brief note in a commit message or CLAUDE.md before clearing context.claude/memory/ files for persistent statefeat/user-auth) to aid context restoration$ARGUMENTS
f499217
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.