handoff

Generates a verified session handoff document with git fingerprint, shipped work, and next tasks.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/ledtorch/coding-agent-workflow --skill handoff-ledtorch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ledtorch/coding-agent-workflow/tree/main/skills/handoff
Command: npx skills add https://github.com/ledtorch/coding-agent-workflow --skill handoff-ledtorch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a coding session ends, the next session starts with zero context, and handoffs written from memory drift from the actual state of the repository. This Skill produces a self-contained handoff document whose every claim is verified against the live git tree before it is written. ## Core Features & Use Cases - Tree-verified claims: Captures branch, status, diff stats, and a HEAD-plus-diff-hash fingerprint at write time, and checks every file path, symbol, and count against the tree before emitting the document. - Drift-detectable pickup protocol: Embeds a fixed Section 0 that instructs the next session to verify the fingerprint, report drift, recommend next work, and wait for the user before touching code. - Reconciled task list: Classifies the prior handoff's tasks as finished, dropped, or still open so completed work never reappears as a pending task. - Use Case: After a long feature-building session, run the handoff command to produce a markdown document the next agent can paste in and immediately know what to read, what shipped, and what to propose next. ## Quick Start Ask the agent to generate a handoff document for this session, optionally providing a file path such as .claude/handoffs/2026-07-26-feature.md to save it to disk.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off a coding session to a new agent with no context?▼

Run the handoff command at the end of the session. It captures the current branch, git status, and a diff hash, then writes a markdown document with reading prerequisites, what shipped, and next tasks that the new session can paste in directly.

How do I prevent a handoff document from drifting out of sync with the repository?▼

The handoff embeds a fingerprint line containing the HEAD commit, modified and untracked file counts, and a hash of the uncommitted diff. The next session compares these three signals against the live tree before trusting any claim in the document.

Can I save the handoff document to a file instead of the chat?▼

Yes. Pass a file path as an argument, such as .claude/handoffs/2026-07-26-topic.md, and the document is written there with the Write tool, creating the directory if needed. Without an argument it is printed to chat for copy-paste.

Why does the handoff tell the next agent not to build immediately?▼

The fixed pickup protocol requires the next session to verify the fingerprint, report what drifted, and recommend which task to start, then wait for the user to choose. This prevents a fresh agent from treating imperative task titles as authorization to execute.

What are the limitations of the git diff fingerprint for detecting changes?▼

The diff hash misses the content of untracked files, though the untracked count notices when they appear. Only a file mtime spot-check at pickup catches untracked content changes, which the document acknowledges as an accepted residual.