Handoff
Write a rich session handoff to a pause-*.md file — checklist, decisions, files changed, self-critique, and a verbatim-id "coordinate closet" — so a fresh session can resume the work after /clear (via the auto-resume hook, or /session-resume). Use before you /clear with work still in flight. Triggers on `/handoff`, "write a handoff", "snapshot this session so I can resume later".
Install
npx skills add iamneilroberts/claude-skills --skill handoffgit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/handoff ~/.claude/skills/handoffPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Write Handoff (auto-loaded on next /clear)
Write a rich session handoff to the **`pause-*.md` namespace**. If you run the optional
`hooks/auto-resume.sh` (bundled in this collection), it loads the newest such file automatically on
your next `/clear`, so the fresh session picks it up with zero effort. Without the hook, resume it
manually with `/session-resume`.
> Why `pause-` and not `handoff-`: the `auto-resume.sh` hook globs `pause-*.md` only. The
> `handoff-*.md` prefix is reserved for long-lived multi-session coordination docs and is
> intentionally NOT auto-loaded. So this command writes `pause-<date>-<topic>.md` even though it's a
> "handoff" — that prefix is what guarantees pickup.
## Steps
1. **Gather git state** (run these):
- `git rev-parse --show-toplevel` (repo/worktree root — resolves correctly inside a worktree)
- `git branch --show-current`
- `git status --short`
- `git diff --stat`
- `git log --oneline -8`
2. **Summarize from this session's memory** — write these sections:
- **What Was Accomplished** — completed work with file paths / commit SHAs
- **Decisions Made** — key choices + rationale
- **Files Created or Modified** — table: path · action · why
- **Checklist** — snapshot your **current TodoWrite list** as GitHub-style
boxes: `- [x]` for completed/`- [ ]` for pending/in-progress. This is the
part that vanishes on `/clear` unless you write it down. If you have noDetails
- Skill name
handoff- Repository
- iamneilroberts/claude-skills
- Path
skills/handoff/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Handoff skill do?
Write a rich session handoff to a pause-*.md file — checklist, decisions, files changed, self-critique, and a verbatim-id "coordinate closet" — so a fresh session can resume the work after /clear (via the auto-resume hook, or /session-resume). Use before you /clear with work still in flight. Triggers on `/handoff`, "write a handoff", "snapshot this session so I can resume later".
How do I install the Handoff skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill handoff. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Handoff popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/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
Branch
37iamneilroberts/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".
Claude Code Best Practices
37iamneilroberts/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.
Process Faq
32joneqian/claude-skills-suite
Process and transform FAQ documents (xlsx, word, pdf, txt) into RAG-optimized format. Use when working with FAQ files, knowledge base documents, or when the user needs to analyze and restructure FAQ content for RAG systems.
PyPDFForm
57javimosch/supercli
Use this skill when the user wants to fill and generate PDF forms
Session Resume
37iamneilroberts/claude-skills
Load a session handoff file and resume the work it describes. Use when the auto-resume hook doesn't apply — a new terminal, or an older handoff you want to pick up by hand.
Browse the most popular Claude skills, all documents & office files skills, or write your own with the skills generator.