← ClaudeAtlas

session-pickuplisted

Start a continued Claude Code session by rehydrating from a prior session's handoff, the inverse of session-end. Reads the latest handoff in .claude/handoffs/ and what it points to, reconciles it against current git and file state to catch drift, rebuilds the todo list, settled constraints, and open verification debts, then presents the immediate next action and confirms before acting.
BryceEWatson/claude-global-skills · ★ 0 · AI & Automation · score 71
Install: claude install-skill BryceEWatson/claude-global-skills
# session-pickup Resume a prior session with zero loss and zero false confidence. Pairs with `session-end` (which wrote the snapshot). Your job is to rehydrate *and reconcile* — then hand control back to the operator at the right decision point, not to barrel ahead. ## Operating principle: a handoff is a SNAPSHOT — trust, then verify The handoff was true when written. Between then and now, things may have moved: commits landed, the branch changed, another session advanced or abandoned the in-progress work, files were renamed. **Never resume blindly on the handoff's word — reconcile it against current reality first.** This is the inverse of session-end's "ground in artifacts": there you grounded the summary; here you ground the resume. ## Step 1 — Locate the handoff - Default: in `<primary-checkout>/.claude/handoffs/`, the newest handoff **whose `<!-- session-end:origin branch=… worktree=… -->` stamp matches the branch you are resuming** (prefer the full handoff doc; also read its companion continuation-prompt file if one exists). - **Never take "newest" on faith when the candidates disagree.** That directory is shared: it lives in the primary checkout so handoffs survive worktree cleanup, which means concurrent sessions in different worktrees all write into it. Picking purely by recency will hand you the handoff of whichever session happened to finish last, and resuming another branch's work is a *silent* wrong start, not a visible error. So: - Match on the