catchup
Restore context after /clear by summarizing recent work and project state
What this skill does
# Context Catchup Restore context after `/clear` - summarize recent work and project state. ## Purpose 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 ## Instructions ### Step 1: Git History Analysis ```bash # 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 ``` ### Step 2: Recent Changes Summary ```bash # 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 ``` ### Step 3: TODO/FIXME Scan ```bash # 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 ``` ### Step 4: Project State Check ```bash # 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" ``` ## Output Format Provide a structured summary: --- ### ๐ Context Restored **Project**: [name from package.json/Cargo.toml/etc] **Branch**: [current branch] **Last Activity**: [time of last commit] ### ๐ Recent Work (Last 5 Commits) 1. [commit message 1] - [files affected] 2. [commit message 2] - [files affected] ... ### ๐ Uncommitted Changes - [list of modified files with brief description of changes] ### โ ๏ธ Outstanding TODOs - [file:line] TODO: [description] - [file:line] FIXME: [description] ### ๐ฏ Suggested Next Steps Based on recent activity: 1. [Most likely next action based on patterns] 2. [Alternative focus area] --- ## Usage Examples **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 ## Pro Tips 1. **Document before `/clear`**: Write a brief note in a commit message or CLAUDE.md before clearing context 2. **Use with Memory Bank**: Combine with `.claude/memory/` files for persistent state 3. **Branch naming**: Use descriptive branch names (e.g., `feat/user-auth`) to aid context restoration $ARGUMENTS
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.