gitwtfhub

wtf is claude-code-handoff-skill?

ostikwhy-blip/claude-code-handoff-skill — explained in plain English

Analysis updated 2026-05-18

22Audience · developerComplexity · 1/5LicenseSetup · easy

TL;DR

A Claude Code skill that writes a verified handoff file so a fresh coding session can pick up exactly where an earlier session left off.

Mindmap

mindmap
  root((handoff skill))
    What it does
      Writes verified HANDOFF.md
      Bridges Claude sessions
      Tags verified vs recalled claims
    Tech stack
      Claude Code
      Git
      Markdown
    Use cases
      Resume long sessions cleanly
      Avoid repeating dead ends
      Archive past handoffs
    Audience
      Developers
      Claude Code users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Hand off a long, messy Claude Code session to a fresh one without losing context.

REASON 2

Keep a written record of failed approaches so they are not retried in the next session.

REASON 3

Recheck previous progress claims against the real repo state before continuing work.

REASON 4

Archive past session handoffs while carrying forward still-relevant dead ends.

What's in the stack?

Claude CodeMarkdownBash

How it stacks up

ostikwhy-blip/claude-code-handoff-skillaerdelan/housand-domaintoolmatrixaffaan-m/opencode
Stars222222
LanguageTypeScriptTypeScript
Last pushed2026-02-09
MaintenanceMaintained
Setup difficultyeasyeasyeasy
Complexity1/52/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

No dependencies or configuration, just copy the folder into .claude/skills.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

Wtf does this do

claude-code-handoff-skill is a small add-on skill for Claude Code, the AI coding assistant, that solves a specific problem: long coding sessions tend to degrade over time. As a session goes on, the AI can start forgetting earlier decisions, retrying approaches that already failed, and describing files in ways that no longer match reality. Starting a brand new session fixes that degradation, but normally throws away everything the old session had learned. This skill fixes that by writing a file called HANDOFF.md at the root of your project. Running the command /handoff at the end of a session tells Claude to check the real state of your repository and write this file, so the next session can pick up exactly where the previous one stopped, without repeating the same dead ends. At the start of a new session, saying "resume from the handoff" tells Claude to read that file, recheck it against the current state of the repository, raise any open questions, confirm the plan with you, and then continue working. The key idea is that nothing gets written into the file purely from memory. Before writing anything, Claude runs git status, git log, and git diff to see what actually changed in the repository, rereads every file the handoff will mention to catch anything that has since changed, and reruns your tests so a claim like tests pass is only written if it was just confirmed. Every statement in the file is labeled either verified, meaning it was checked during this handoff, or as recalled from memory and not yet rechecked. The resulting file is kept to roughly 250 to 400 lines and covers the current goal and verified state, the decisions made and why, failed approaches and the exact reason they failed, known traps found in the codebase, an ordered list of next steps, and open questions only the user can answer. Older handoff files are not deleted, they get archived into a .handoffs folder, and dead ends that are still relevant get carried forward automatically. Installation is a simple git clone followed by copying the folder into the .claude/skills directory, either globally or for a single project, with no other dependencies or setup required. The project is released under the MIT license.

Yoink these prompts

Prompt 1
Help me install the handoff skill globally in my ~/.claude/skills directory.
Prompt 2
Run /handoff at the end of my current Claude Code session and explain what it writes.
Prompt 3
Show me how to resume a project using an existing HANDOFF.md file.
Prompt 4
Explain the difference between the verified and recalled-from-memory tags in a handoff file.

Frequently asked questions

wtf is claude-code-handoff-skill?

A Claude Code skill that writes a verified handoff file so a fresh coding session can pick up exactly where an earlier session left off.

What license does claude-code-handoff-skill use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is claude-code-handoff-skill to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is claude-code-handoff-skill for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.