handoff

Generates a structured handoff.md file capturing current work state for cross-machine session continuity.

2|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/spideynolove/claude-dotfiles --skill handoff-spideynolove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/spideynolove/claude-dotfiles/tree/main/.claude-global-backup/skills/handoff
Command: npx skills add https://github.com/spideynolove/claude-dotfiles --skill handoff-spideynolove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you switch machines mid-task or end a session with unfinished work, context is lost and the next session wastes time reconstructing what was happening. This Skill captures the current work state in a standardized .claude/handoff.md file that is committed to git and automatically loaded on the receiving machine. ## Core Features & Use Cases - Structured Handoff Template: Generates a handoff file with fixed sections covering current task, next steps, open questions, decisions made, files in flight, and blockers. - Git-Based Sync: Commits and pushes the handoff file so any machine that pulls the repository receives the latest work state. - Automatic Reload: On the receiving machine, a session-start hook injects the handoff content without manual action. - Use Case: You are halfway through adding rate limiting to an API on your desktop. Before leaving, invoke the Skill to write a handoff listing the exact next edit, then pull the repo on your laptop and resume immediately. ## Quick Start Ask the AI to generate a handoff file summarizing the current work state before ending this session.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer Claude Code session context between machines?

Generate a .claude/handoff.md file summarizing the current task, next steps, and open questions, then commit and push it to git. On the receiving machine, a session-start hook automatically injects the handoff content when you pull the repository.

What should a work handoff document include?

A handoff should include the current task in one sentence, concrete actionable next steps, open questions, decisions that could be re-litigated, files with uncommitted changes, and any blockers. Omit sections that are empty.

Does the handoff file sync automatically across computers?

The handoff syncs through git: the Skill commits and pushes .claude/handoff.md, and any machine that pulls the repo receives it. A context-loader hook injects the file on session start without manual steps.

When should I delete the handoff file?

Delete .claude/handoff.md once the work is complete, such as when the feature is merged or the task is done. Commit the deletion with a message like 'chore: clear handoff' so all machines drop the stale state.

What are the limitations of file-based session handoffs?

The handoff only captures a written summary, not full conversation history or uncommitted code changes. Files in flight must still be committed or stashed separately, and the summary quality depends on how concrete the next steps are written.