Use when writing a Codewhale takeover prompt, continuation note, or end-of-session summary for another agent or a later session: a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
A handoff is read by an agent with none of your context and every incentive to believe you. That makes an optimistic handoff worse than no handoff: it converts your guesses into the next session's premises. Write it so the reader can re-derive the state instead of trusting the prose.
Stage 6 of the loop, and the one that makes the loop a loop: the next session starts at cw-orient with what you leave here.
Write it as a prompt the next agent can paste directly. Not a report about the work — instructions for continuing it.
Open with the refresh block, not with your summary. The first thing the reader should do is verify you:
cd <repo path>
git status --short --branch && git branch --show-current
git log --oneline --decorate -20
git log --oneline origin/main..HEAD
./scripts/release/check-versions.shTell them to trust that output over anything below it.
Cover these, in whatever order fits; drop sections that are empty:
main.main
(AGENTS.md). Tag, GitHub Release, publish, deploy, PR merge and
destructive cleanup need explicit approval. A task scoped local-only says
so.AGENTS.md for
the area, then the specific docs (docs/CACHE.md,
docs/MOTION_CONTRACT.md, docs/ARCHITECTURE.md, crates/tui/AGENTS.md)
the task actually touches.Separate three states, and never blur them: done and verified (with the command output that proves it), suspected (a hypothesis, labeled), and blocked (with what unblocks it). If you did not run it, it is not done.
Say what is unpushed and why. A commit ahead of origin/main is either
waiting on a check (name it) or blocked (name the blocker).
Record missing external receipts. If the task was local-only, say which evidence you could not gather (CI state, registry state, review threads) rather than inferring it. A named gap is useful; a confident guess is not.
Before writing the handoff, run the record backstop and list anything it shows as owed:
git log --format='%h %s' "$(git log -1 --format=%H -- CHANGELOG.md)"..origin/main | grep -E '^[0-9a-f]+ (feat|fix)'
python3 scripts/check-contributor-credit.pyA single paste-ready block with the default shape — refresh commands, authority line, files to read, landed SHAs, named dirty files, prioritized next slices, the verification gate, and the open decisions — with done / suspected / blocked visibly separated. Compress when trivial, but never compress away the state separation: that is what keeps guesses from becoming the next session's premises.
Hmbown/Codewhale
3e1359f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.