Pickup

Use when the user wants to pick up / resume the most recent handoff in an isolated worktree — finds the newest handoff doc, RESUMES the worktree/branch it documents if one exists (re-adding it if parked), otherwise creates a fresh branch + worktree, then loads the handoff's context so work continues where it left off. Triggers on `/pickup`, "pick up the handoff", "resume the latest handoff in a worktree", "branch and continue". Distinct from `session-resume` (loads a handoff in-place, never branches) and `branch` (makes a worktree, loads no handoff) — `/pickup` does both, reusing an existing w

37 stars 7 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill pickup
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/pickup ~/.claude/skills/pickup

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Pickup

Resume the newest handoff in an isolated worktree, then load its context. Reuse the documented worktree/branch if it still exists; create a new one only when none is documented or it's gone. Orchestrates `branch` and `session-resume` — do not reimplement their internals.

> **Requires `branch` and `session-resume`** from this collection (optionally `/pm`, see step 1 tip). Install alongside this skill.

## Steps

1. **Find the handoff.** Use `session-resume`'s discovery (shared `handoffs/` dir, then legacy in-tree dirs). Prefer newest *intentional* `pause-*.md`; fall back to a *mechanical* `auto-*.md` only if none exists. Path arg → use it. Date/topic/slug arg → filter by it. No arg → newest intentional handoff. Multiple matches → list the 5 most recent and ask. None → say so, stop. Read the file. Tip: run `/pm` first for a picture of all in-flight lanes.

2. **WIP/worktree safety first.** Run `git worktree list` and read the shared journal (`$(bash ~/.claude/coordination/resolve-coord-dir.sh)/journal.md`; the in-tree `docs/worktree-journal.md` is only a tombstone pointer). If another session has uncommitted WIP or an overlapping active worktree, surface it and pause. Never branch on top of another session's WIP.

3. **Resume-or-create.** Check the handoff + journal for a documented branch/worktree (`Branch:`/`Worktree:` line, `## Parked` entry, or an "Active" journal entry):
Read the full skill on GitHub

Details

Skill name
pickup
Path
skills/pickup/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Pickup skill do?

Use when the user wants to pick up / resume the most recent handoff in an isolated worktree — finds the newest handoff doc, RESUMES the worktree/branch it documents if one exists (re-adding it if parked), otherwise creates a fresh branch + worktree, then loads the handoff's context so work continues where it left off. Triggers on `/pickup`, "pick up the handoff", "resume the latest handoff in a worktree", "branch and continue". Distinct from `session-resume` (loads a handoff in-place, never branches) and `branch` (makes a worktree, loads no handoff) — `/pickup` does both, reusing an existing w

How do I install the Pickup skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill pickup. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Pickup popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Sweep

37

iamneilroberts/claude-skills

Use when work may have been dropped between sessions — after a crash, a lockup, parallel-session churn, or on a "did we drop anything?" hunch. Crawls worktrees, local AND remote branches, stashes, deploy targets, and intent docs (handoffs, checklists, plans, coordination journals); triages every item against ground truth (patch-id merge equivalence vs fetched origin/main, live BUILD_SHA/bundle provenance, PR state); presents a ranked loose-end ledger for ONE batch approval; then methodically recovers approved items via playbooks (adopt stray WIP, resume handoffs, rebase→test→push→PR). Never de

Git & Code Review

Idea

37

iamneilroberts/claude-skills

Capture a fix / feature / research idea fast and turn it into a tracked GitHub Issue plus a lightweight planning doc, so nothing gets lost and it shows up next time you list your issues. Runs a short confirm-or-edit interview (infers title/slug/type from your one-liner, you accept or correct), writes docs/ideas/<date>-<slug>.md, files a labelled GitHub Issue via gh, and backlinks the issue URL into the doc. Triggers on `/idea <one-liner>`, `/idea`, "capture this idea", "file an idea", "log a thing to fix/build/research", "remember to look into X".

Git & Code Review

Diff Review

42

robbyt/claude-skills

Get Google Antigravity's (`agy`) code review of git changes after Claude makes edits. Trigger when user wants a second opinion on code changes ("have agy review my changes", "get code review from Google Antigravity", "review this diff with agy"), or as a final check before committing. Replaces the deprecated gemini-cli diff-review workflow.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.