One-click install
npx skills add https://github.com/ostikwhy-blip/claude-code-handoff-skill --skill handoff-ostikwhy-blip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ostikwhy-blip/claude-code-handoff-skill/tree/main
Command: npx skills add https://github.com/ostikwhy-blip/claude-code-handoff-skill --skill handoff-ostikwhy-blip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill prevents long Claude Code sessions from losing decisions, repeating failed approaches, or relying on stale file descriptions by creating a verified HANDOFF.md for the next session.

Core Features & Use Cases

  • Verified session handoffs: Reconstructs repository state with git status, git log, git diff, fresh file reads, and current test or build output before writing claims.
  • Resume with drift detection: Reads and re-verifies an existing HANDOFF.md, reports changes against its recorded Git state, surfaces open questions, and confirms the adjusted plan.
  • Dead-end preservation: Archives older handoffs and carries forward failed approaches, known traps, verified state, and concrete next steps so future sessions avoid repeating mistakes.
  • Use Case: When context is running low after a complex implementation, run a handoff so a fresh Claude Code session can resume from verified repository facts instead of an unreliable summary.

Quick Start

Use the handoff skill by asking Claude Code to run /handoff before ending the session, then ask the next session to resume from the handoff.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve context when starting a new Claude Code session?

You preserve context by generating a verified HANDOFF.md file that captures the current repository state, test outputs, and git diffs for the next session to read and resume work.

What is context degradation in long coding sessions and how do I prevent lost work?

Context degradation happens when a long session loses track of decisions or relies on stale file states. Prevent lost work by running a handoff to archive verified repository facts and dead-ends before the context window fills.

How do I resume a complex coding task from an existing handoff file?

You resume a coding task by reading the existing HANDOFF.md, which re-verifies the recorded Git state, surfaces any drift or changes, and confirms the adjusted plan before continuing implementation.

Does Claude Code session handoff verify repository state before writing context files?

Yes, session handoff verifies repository state by inspecting git status, git log, git diff, executing current tests, and reading fresh files before writing any claims to the handoff file.

Can I track failed approaches and dead-ends across multiple Claude Code sessions?

Yes, you track failed approaches and dead-ends by archiving older handoff files and carrying forward known traps and verified states so future sessions avoid repeating the same mistakes.