pickup

Resumes prior session work from checkpoint resume blocks via pickup-list.

1|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/mark-brannan/dotfiles --skill pickup-mark-brannan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pickup
Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/pickup
Command: npx skills add https://github.com/mark-brannan/dotfiles --skill pickup-mark-brannan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Claude Code session ends mid-work, the next session normally has to re-survey the project and re-decide what to do. This Skill reads the resume block the previous session wrote into its checkpoint and restarts work directly from that hand-off, avoiding duplicated planning and conflicting worktree claims. ## Core Features & Use Cases - Resume block discovery: Runs pickup-list to enumerate resumable branches, selecting one automatically or asking for a one-line pick when several exist. - Safe worktree handling: Forks a fresh worktree with EnterWorktree instead of reusing the previous session's directory, and stops cleanly when a branch is still claimed by a live session. - Consumption tracking: Appends a consumed line to the checkpoint's ## Resume block so the same hand-off is never picked up twice. - Block authoring: Defines the four-line hand-off format (next, link, model, effort) a leaving session writes into its own checkpoint. - Use Case: You return to a project after a session ended mid-PR. Say "pick up where we left off" and the Skill restates the next step, checks out the branch in a new worktree, marks the block consumed, and starts work. ## Quick Start Say "pick up where we left off" or "/pickup <branch>" to resume the work a previous session handed off in its checkpoint.

Frequently Asked Questions about pickup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a previous Claude Code session's work?▼

Say "resume", "pick up", or "/pickup" and the Skill runs pickup-list to find resume blocks left in prior checkpoints. It restates the next step, checks out the named branch in a fresh worktree, and marks the block consumed.

How do I hand off unfinished work to a future session?▼

Push your branch, then write a four-line `## Resume` block in your own checkpoint with next, link, model, and effort fields. The next session's pickup-list will surface it, and the block drops automatically once the branch merges or goes level.

Why can't I reuse the previous session's git worktree?▼

The owning session may still be running and could be archived mid-turn, so no-foreign-worktree.sh refuses access. The Skill forks a new worktree with EnterWorktree and checks out the branch from the pushed remote state instead.

What happens if the branch is checked out in another worktree?▼

Git refusing the checkout means a live session still claims that branch. The Skill names the branch and worktree, then stops rather than taking over or working the same branch elsewhere.

When should I write a resume block instead of a full wrap-up?▼

Write a resume block when the hand-off fits in four lines and the state lives on a branch, PR, or issue. A full /wrapup is only for sessions holding context that no issue, PR, or card can carry.