Claude Code · Free Kit
100% FREE

Claude Code Handoff Kit

Every fresh Claude Code session starts from zero on your project. This kit writes the small file that fixes it, so tomorrow's session picks up right where today's stopped, without you re-explaining the whole project.

01

The problem nobody warns you about

Close a Claude Code session and three things happen to your work.

Fresh sessions start at zero

New window, blank memory. The project you spent all day explaining? Gone. You get to explain it again.

every session

Summaries can drop the dead ends

Compaction and auto-summaries keep your decisions but can quietly lose the approaches that didn't work. Then the next session happily re-runs them.

the hidden cost

Re-explaining burns real time

20 minutes of "so here's the project, here's where we were" at the start of every session adds up fast. And it buries the new session in pasted history.

your time
02

How it works

One command at the end. One line at the start. That's the whole loop.

  1. End your session with /handoff. The skill sweeps for unresolved mistakes (it reports them, it never silently "fixes" your code), then writes a lean checkpoint: goal, exact stop point, verification evidence, next action, and every dead end you paid for.
  2. It saves a lean checkpoint (target: ~30 lines) outside your repo with a state header: branch, commit, and dirty-file counts pulled straight from git. Then it prints your resume line.
  3. Next session, paste one line. The fresh session reads the file, checks your repo's live state against the header before touching anything, restates the plan in 3 lines, and starts working.
Read ~/.claude/handoffs/my-project.md and continue
03

The part that makes it different

Everyone has a notes template. Almost nobody ships the verification step.

Blind resume

  • "Read my notes and continue"
  • Trusts a file that might be days old
  • Doesn't know a teammate (or you, in another window) already changed the code
  • Starts editing based on stale state

Verified resume

  • Compares the handoff's branch, commit, and dirty counts against live git
  • Reports any mismatch BEFORE changing files
  • Restates Goal / State / Next in 3 lines so you can sanity-check it
  • Then, and only then, starts the next step
fresh session · repo changed since the handoff was written
$ Read ~/.claude/handoffs/demo-repo.md and continue

Mismatch found: the tree is now clean at HEAD 84a0ec7 (commit "notes +
gitignore"). The README scratch line and notes.json from the handoff are
gone, resolved by a commit made outside this session.

Nothing pending. Waiting on you for what's next.

That catch above is real output from our test run. The handoff said commit e911e9d, the repo had moved to 84a0ec7, and the fresh session stopped and said so instead of editing files based on stale info. We call the header a drift tripwire: a mismatch reliably means stop and look. That's honest, and it's a big upgrade over an undated notes file.

04

What's in the kit

Self-contained. No dependencies, no build step, nothing phones home.

The /handoff skill

Drop one folder into Claude Code and end any session with /handoff. Includes the git state-header script.

claude code30-sec install

The portable prompt

Zero install. Paste it at the end of any session. Works in Claude Code out of the box, and in Cursor, Codex, and friends (any agent that can write files in your home folder).

any harnessno setup

START-HERE guide

Open it in your browser: install, first handoff, resume, uninstall. Copy buttons on everything you'd type.

humans

A real example handoff

Generated by the skill on a demo repo, not written by hand. See exactly what you'll get before you install anything.

real output

The policy one-pager

The rules that make it work: when to hand off, why you never trim the failed approaches, and why the resume verifies first.

the procedure

Compatibility & honest limits

What's supported, what's not, and what a handoff can't save (unsaved buffers, killed processes). No overselling.

tested
05

A real generated handoff

Excerpted from a real handoff the skill generated during testing (shortened to fit here, username redacted). Note the mistake sweep: the session found changes it didn't make, and flagged them instead of touching them.

~/.claude/handoffs/demo-repo.md
# Handoff — demo-repo — status: ready
timestamp: 2026-07-17 06:53 CDT
cwd: /home/alex/projects/handoff-kit/demo-repo
branch: master · head: e911e9d · dirty: staged=0 unstaged=1 untracked=2

RESUME RITUAL: compare repo_root+branch+head+dirty against live git status;
report any mismatch BEFORE changing files. Then state Goal/State/Next
in 3 lines and start Next 1 in the same turn unless blocked.

## Goal — demo-app: tiny todo CLI. No active task this session.
## State — tree picked up two changes this session didn't make:
  README.md gained "# scratch note", untracked notes.json appeared.
## Evidence — git status --porcelain → M README.md, ?? notes.json
## Next — 1. Ask whether those changes are wanted, before touching them.
## Tried / constraints — none this session.
(...decisions, key files, open items...)

Resume: Read ~/.claude/handoffs/demo-repo.md and continue

Privacy rule, stamped on every section: the skill's rules bar secrets, tokens, credentials, auth URLs, customer data, and copied file contents from every handoff. Safe paths and redacted excerpts only. (It's an instruction the model follows, not encryption, so glance at the file before sharing it.) The file lives outside your repo, so it never lands in a commit.

06

Get it

Free. The download includes everything above, and grabbing it through Gumroad means you get fixes and new versions by email.

Honest version: if all you want is the paste prompt, it's in the kit and it works with zero setup. Install the skill when you're tired of pasting. Either way you stop re-explaining your project every morning.

A handoff isn't a transcript. It's the 30 lines your repo can't tell a fresh session, verified before they're trusted.

/handoff → close the window → "read the file and continue"