session-handoff

Generates a pasteable prompt summarizing finished session work for handoff to another Claude Code session.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill session-handoff-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/session-handoff
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill session-handoff-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When work spans multiple Claude Code sessions, context is lost between them. This Skill turns what a session finished — code on a branch, an open change request, tracker updates, or findings-only investigations — into a structured prompt that another session can paste in and act on without re-discovering the state. ## Core Features & Use Cases - Structured handoff prompt: Produces a prompt carrying the result, the branch or location of the work, every change request and issue touched, and ordered next steps for the receiving session. - Two postures: Distinguishes answering an order from hcb-dev:session-dispatch (returns the tag and reconciles against the ask) versus unbidden work offered to the user. - Findings-only support: When no files changed, carries verified findings at repo-relative coordinates with revision and verification status instead of a change list. - Use Case: You finished a bug fix on a branch in one session and want a fresh session to review and merge it. Run the handoff skill to produce a prompt listing the branch, the PR state, every issue touched, and the exact steps the new session should follow. ## Quick Start Ask the skill to package this session's finished work into a handoff prompt I can paste into another Claude Code session.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I hand off work between Claude Code sessions?▼

Use the session-handoff skill to generate a pasteable prompt containing the result, the branch or change request location, every issue touched, and ordered next steps. Paste that prompt into the new session so it can verify and continue the work.

What is the difference between session-handoff and session-dispatch?▼

Session-handoff packages work that is already finished for another session to receive. Session-dispatch is for work not yet done that another session is asked to implement. The discriminator is whether the work is done, not how the request is worded.

Can session-handoff transfer investigations that changed no files?▼

Yes. When no files changed, the prompt carries the findings themselves: each claim at a repo-relative file and line with the revision it was read at, its verification status, what was ruled out, and what was never checked.

Does the handoff prompt include issues that were only commented on?▼

Yes. Every touched change request and issue gets a line, including issues only commented on, closed by a merged PR, or deleted. The complete list prevents the receiving session from misreading dead issue numbers.

When should I not use session-handoff?▼

Do not use it for work that is not yet done — use session-dispatch instead. A batch answering its master session in a wave workflow should return per the wave-worker skill rather than through a handoff prompt.