Menu
Restore context after /clear — git state, branch, sprint, recent commits. Lightweight context recovery without starting work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guidance for editing Claude Code agents. Use when Claude touches agent markdown files so tool scopes, MCP wiring, memory scope, isolation, and agent hooks are configured safely.
Guidance for editing Claude Code hooks. Use when Claude touches hook scripts, hook JSON, or settings files that register hooks so matcher selection, shell choice, timeouts, and blocking behavior stay correct.
Automatic memory extraction skill — triggered by file operations to extract durable learnings from session context. Runs in the background via the memory-extractor agent.
Guidance for editing Claude Code skills. Use when Claude touches skill folders or SKILL.md files so slash-command naming, frontmatter, helper scripts, and conditional paths stay coherent.
BOM (Bill of Materials) management for electronics projects — the primary orchestrator skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills into a unified workflow. Create, update, and maintain BOMs with part numbers, costs, quantities stored as KiCad symbol properties. ALWAYS trigger this skill for any task involving component sourcing, pricing, ordering, distributor searches, BOM export, or fabrication preparation — even if the user names a specific distributor or fab house (e.g. "search DigiKey for...", "generate JLCPCB BOM", "order from Mouser"). This skill decides which distributor/fab skills to invoke and in what order. Also trigger on phrases like "what parts do I need", "order components", "how much will this cost", "export for JLCPCB", "find parts for this board", "cost estimate", "compare pricing", or "check stock".
Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API-based method for fetching datasheets. Find parts by keyword or part number, check pricing/stock, download datasheets directly via API, analyze specifications. Sync and maintain a local datasheets directory for a KiCad project — extract components from schematics, download all missing datasheets, keep them up to date. Use with KiCad for BOM creation and part selection. Use this skill when the user asks about electronic components, part specifications, datasheets, footprints, pricing, stock availability, or needs to download/read a datasheet — even if they don't mention "DigiKey" by name. Also use when the user says "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping and the preferred datasheet source because its API returns direct PDF links without web scraping. For package cross-reference t
| name | catchup |
| description | Restore context after /clear — git state, branch, sprint, recent commits. Lightweight context recovery without starting work. |
| metadata | {"version":"2.0","effort":"low","auto-invocable":false,"category":"workflow","compatible-claude-code":{"when_to_use":"After /clear to restore project context","allowed-tools":["Bash","Read"]}} |
Usage: /catchup [branch]
Restore context after /clear. Use $ARGUMENTS for optional branch name.
Git state — run in parallel:
git log --oneline -15 (or on the specified branch)git diff --stat HEADgit statusgit branch --show-currentProject state — read these files (skip missing ones):
TASKS.md — first 30 lines (current sprint)CHANGELOG.md — first 25 lines (latest version entry)memory/MEMORY.md — if it exists, skim for "Current State"Output format — print a concise summary:
Branch: <branch>
Version: <version from CHANGELOG>
Sprint: <number> — <theme>
Active tasks: <task numbers and one-line summaries>
Uncommitted: <file count> files changed
Recent work: <1-2 sentence summary of last 5 commits>