Handoff
π» The friendly ghost in your git. Your AI said done β Casper makes it prove it. Claim-evidence hooks + a verdict ledger for Claude Code.
npx -y skills add ronniepinnell/casper --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Context-rot prevention: write a structured handoff document capturing the current session state so you can /clear and continue in a fresh session without losing context. Use when: context >70%, session >15 turns, hitting limits, or switching tasks mid-work. Invoke: /handoff [optional-filename]
SKILL.md
2.1 KB, 456 tokens by cl100k_base, as published. Nobody here has run it
/handoff β Session Handoff Document
Write a structured handoff doc to docs/state/handoffs/YYYY-MM-DD-HH-MM.md (or user-specified path).
Steps
-
Determine output path:
docs/state/handoffs/<YYYY-MM-DD-HH-MM>.md. Create dirs if needed. -
Write the handoff doc with exactly these sections:
# Handoff β <YYYY-MM-DD HH:MM UTC>
## Branch & Git State
- Branch: <current branch>
- Last commit: <hash> <message>
- Uncommitted: <list files or "clean">
## Goal
<1-2 sentences: what we're trying to accomplish>
## Done This Session
<bulleted list of completed items with file paths>
## Pending / Next Steps
<ordered list of what to do next β be specific, include file paths and line numbers>
## Key Decisions Made
<any non-obvious choices: why X not Y>
## Active Linear Tickets
<BEN-XXXX: title β status>
## Resume Command
Continue from handoff: docs/state/handoffs/<filename>.md
- Print:
Handoff written: docs/state/handoffs/<filename>.md - Print:
Next: /clear β new session β paste: "Continue from handoff: docs/state/handoffs/<filename>.md"
On "continue from handoff <path>"
When a session starts with "Continue from handoff: <path>":
- Read the handoff file at <path>
- Confirm the branch, verify git state
- Resume exactly at "Pending / Next Steps" β no recap needed
- Say: "Resuming from handoff. Next: <first pending item>"
Judgment weave (see /judgment)
The handoff doc must carry the judgment state, or the next session re-derives it: open GATE: lines and their current readings, unresolved /door analyses, UNVERIFIED claims awaiting refutation. Fresh sessions inherit the ledger for free (.claude/verdicts.log is committed) β point at it rather than re-summarizing.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.