catchup
Use after /clear, /compact, session resume, or context loss. Use when branch context is stale or unknown. Use when starting work in an existing worktree.
What this skill does
# Catchup — Context Reconstruction **This skill is strictly read-only. Do NOT edit files, create branches, or run write commands.** ## 1. Gather data (run all independent steps in parallel) - `git log --format="%h %s (%ar)" -20`, `git status`, and `git worktree list` - Read `.branch-context.md` (if exists — check CWD and worktree root). Parse YAML frontmatter: `workflow_step`, `validate_round`/`validate_max`, `review_round`/`review_max`, `plan_review_chunk`/`plan_review_total`/`plan_chunks_approved` - Read `ai-workspace/MEMORY.md` — note anything in-progress or blocking - Read `HANDOFF.md` (if exists) - List `ai-workspace/plans/` (sort by mtime, most recent first) and read the first file that does NOT end in `.done.md` or `.executed.md` - Search Basic Memory via MCP for recent entries matching the current branch name. If MCP unavailable, skip silently. - **GitHub** — check availability first: ```bash command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1 ``` If authenticated, run in parallel: ```bash gh pr list --state open gh issue list --state open --limit 15 ``` If `gh` is unavailable or unauthenticated, note "GitHub CLI unavailable" and skip. Do NOT attempt to install or authenticate. ## 2. Synthesize Present findings in this format. **Omit sections where the data source was not found** (e.g., no HANDOFF.md, gh unavailable). Always show Loop state and Blockers even when empty — absence is informative: ``` Branch: <name> — <what we're building (from plan or branch-context)> Worktree: <path> (or "primary") Last commit: <hash> <message> Uncommitted: <staged/unstaged summary, or "clean"> Workflow step: <N> — <step name> (from frontmatter, or inferred) Loop state: validate <round>/<max>, review <round>/<max> Active plan: <file> — <current phase> — <next action> Blockers: <list> Open PRs: <count — titles> Open issues: <count — top 5 titles> Handoff: <detail> ``` After the summary, **surface blockers and TODO items prominently** — remaining work, failing CI, stale branches, items from memory flagged as blocking. These go above the fold, not as footnotes. ## 3. Suggest next actions Based on gathered state, suggest 2-3 concrete next actions. Examples: - "Resume building — plan X is at step 5 (Build)" - "Run /validate — implementation looks complete" - "Address blocker: [description]" - "Review open PR #N — awaiting action" - "Pick up issue #N — in-progress" End with: "What would you like to do?" ## Failure modes - **No `.branch-context.md`**: infer workflow step from git state and plan file status. Note: "No branch context — step inferred." - **No active plan**: note "No active plan." Do not search `.done.md` files. - **On `main` branch**: skip branch-context and plan lookup. Show git state, PRs, issues, and memory only. - **Basic Memory MCP unavailable**: skip silently. - **`gh` unavailable**: show "GitHub CLI unavailable — PR/issue status unknown."
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.