session-handoff

Generates a detailed session handoff document with git snapshot for context transfer.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/Takkuya/claude-skills --skill session-handoff-takkuya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/Takkuya/claude-skills/tree/main/session-handoff
Command: npx skills add https://github.com/Takkuya/claude-skills --skill session-handoff-takkuya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI coding sessions lose context when you start a new conversation, forcing you to re-explain decisions, failed attempts, and project state. This Skill writes a complete reconstruction of the current session into a local file that the next session can read to resume work with minimal context loss. ## Core Features & Use Cases - Full session reconstruction: Rebuilds the chronological timeline, every file touched, decisions with discarded alternatives, and failed attempts so the next session avoids repeating mistakes. - Git ground truth snapshot: Captures raw output of git status, diff, staged diff, and recent log as an unedited appendix so the narrative can be verified against the real repository state. - Local-only artifact: Writes to .session-artifacts/HANDOFF.md, ensures it is covered by .gitignore, migrates legacy root-level handoff files, and rewrites the whole file on each invocation. - Use Case: Your session has grown long and token usage is high. Ask for a handoff, then open a new session in the same directory and tell the assistant to read .session-artifacts/HANDOFF.md before continuing. ## Quick Start Ask the assistant to generate a complete session handoff saved to .session-artifacts/HANDOFF.md so you can continue in a new session without losing context.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I transfer context between Claude sessions?

Generate a handoff document that reconstructs the session timeline, files touched, decisions, and failed attempts into a local Markdown file. In the new session, open the same directory and instruct the assistant to read that file before doing anything else.

What should a session handoff document include?

A good handoff includes the overall goal, a chronological timeline, every file touched with reasons, decisions with discarded alternatives, failed attempts to avoid repeating, open questions, next steps, and a raw git snapshot as ground truth.

Should I commit the handoff file to git?

No. The handoff file is a local working artifact and should never be committed. The Skill verifies that .session-artifacts/ is covered by .gitignore before writing, and untracks any legacy handoff files with git rm --cached.

Can the handoff output be generated in English instead of Portuguese?

Yes. Pass the --out-locale en-us argument to generate the HANDOFF.md content in English, or --out-locale pt-br for Portuguese. Without the flag, the file follows the language of the current conversation.

Why include raw git diff output in a handoff document?

The raw git snapshot acts as ground truth because session narratives can have gaps or inaccuracies. The next session can verify the written summary against the actual repository state, and truncated diffs are explicitly flagged with recovery instructions.