Claude Handoff Skill

claude-handoff-skill

A [Claude Code](https://claude.com/claude-code) skill that writes a **handoff summary** before you close the current session, so a brand-new session — with zero memory of this one — can pick up exactly where you left off.

Why

Long Claude Code sessions eventually hit context limits, or you just want to start a clean window. Re-explaining what's done, what's next, and *why* you made certain calls wastes time and things get lost. This skill makes Claude gather real evidence (`git status`, `git diff`, `git log`) instead of relying on its memory of the conversation, then writes a compact, structured summary you can hand to the next session.

What it produces

Four fixed sections, in the language you've been using in the conversation:

1. Completed work — what was done, which files were touched, with uncommitted / committed-but-unpushed / stashed changes called out separately
2. Next steps — ordered by priority, each one a concrete action (which file, which command) — never something vague like "keep optimizing"
3. Technical decisions & caveats — only what a new session can't infer from reading the code: why A over B, ruled-out approaches, constraints, files not to touch
4. Suggested first prompt — a copy-pasteable block with the project path, current branch, and the first thing to do, ready to paste into the new session

Kept to one page. It's a handoff, not a report — the new session can read the code for anything not worth repeating here.

Example output

## 1. Completed work
- Added rate limiting to the login endpoint → `src/auth/rateLimiter.ts` (new), `src/auth/login.ts`
- Uncommitted: `src/auth/rateLimiter.ts` has a TODO for the Redis key TTL
- Committed but not pushed: `a3f9c1e fix: correct off-by-one in retry backoff` (1 commit ahead of origin/main)

## 2. Next Steps
1. Decide the Redis key TTL in `src/auth/rateLimiter.ts:42` (currently hardcoded to 60s, marked TODO)
2. Run `npm test src/auth` to confirm th