handover
Skill1 starsChanged 7 months agoMITView on GitHub
End-of-session menu — wrap up this Claude session. Logging, YAML handovers, spawning new instances, clipboard. Triggers on "handover", "end session", "wrap up", "hand off", "session transfer".
51 other projects use a version of this.
Adopted by
Most recently taken up by
- thiagobluhm/o1memtheir own version, first seen Nov 8, 2026
- hmislk/hmistheir own version, first seen Nov 2, 2026
- loonylabs-dev/claude-setuptheir own version, first seen Nov 1, 2026
- oubakiou/skillstheir own version, first seen Nov 1, 2026
- vrppaul/claude-reviewtheir own version, first seen Nov 1, 2026
- konlue/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use harness-init, incident and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
steptianSkillharness-init
初始化 .harness 开发框架,集成代码修改影响范围评估和测试覆盖建议功能。触发词:'初始化新项目'、'harness init'、'更新 harness'、'分析影响范围'、'评估修改影响'
Also in 3 projects that use this
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 3 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 3 projects that use this
GoogleSkillto-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
MicrosoftSkillcaveman
Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules
Also in 3 projects that use this
Other versions51 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 51
- me2resh/apexyard★ 542same name
- hmislk/hmis★ 244same name
- chenklein26-maker/Harness-Starter★ 119same name
- k1ein-chen/Harness-Starter★ 119same name
- eai-org/agent-toolkit★ 85same name
- manusco/resonance★ 38same name
- chacosoldier/compabob★ 34same name
- randommonicle/claude-skills★ 27same name
- L-X-T/ng-agentic-skills★ 13same name
- marcogalluccio/company-brain-os★ 7same name
41 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- claude-and-shellSkill
- claude-gridSkill
- clipboard-handoverSkill
- handover-with-tasksSkill
- new-claude-atSkill
- new-claude-hereSkill
- new-workspaceSkill
- sideclaudeSkill
- spawn-planning-repoSkill
- start-from-handoverSkill
- start-leftoverSkill
- terminal-hereSkill
- vscode-hereSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Write minimal YAML HANDOVER.md
- Very specific: line 56
Write JSON log to Agent-Logs (check memory for path, fall back ~/repos/github/my-repos/Agent-Logs/)
- Very specific: line 57
Commit, push, run python3 scripts/ingest.py if exists
- Very specific: line 69
If missing, suggest /session-transfer:setup-agent-logs.
- Distinctive: line 80
Write log (same as Choice 5)
- Distinctive: line 91
No files, no spawn
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Handover Menu
Single entry point for all end-of-session workflows.
When to use
- User says "handover", "hand off", "wrap up", "end session", "session transfer", "pass the baton"
- Context getting long, switching task/repo
Procedure
1. Present menu
Display exactly:
How do you want to wrap up?
1. Full handover + new session — investigate repo, write YAML HANDOVER.md, spawn new Claude
2. Quick handover + new session — minimal YAML HANDOVER.md, spawn new Claude
3. Log + full handover + new session — archive to Agent-Logs, then full handover + spawn
4. Write handover only — create YAML HANDOVER.md, stay in this session
5. Log only — record to Agent-Logs, no handover, no spawn
6. Log + spawn (no handover) — archive log, spawn fresh Claude with no context
7. Clipboard handover — short YAML summary in chat + copied to clipboard, no files, no spawn2. Wait for choice
Accept 1-7 or keyword ("quick", "log only", "full", "clipboard").
3. Execute
Choice 1: Full handover + new session
Run /session-transfer:handover:
- handover-writer subagent creates YAML
HANDOVER.md - Verify exists
konsole --workdir "$(git rev-parse --show-toplevel)" -e claude "/session-transfer:start-from-handover" &- Report
Choice 2: Quick handover + new session
Run /session-transfer:quick-handover:
- Capture git state
- Write minimal YAML HANDOVER.md
- Commit and push
konsole --workdir "$(git rev-parse --show-toplevel)" -e claude "/session-transfer:start-from-handover" &- Report
Choice 3: Log + full handover + new session
Run /session-transfer:log-and-handover:
- Write JSON log to Agent-Logs (check memory for path, fall back
~/repos/github/my-repos/Agent-Logs/) - Commit, push, run
python3 scripts/ingest.pyif exists - handover-writer subagent creates YAML
HANDOVER.md - Spawn + report
Choice 4: Write handover only
Run /session-transfer:write-handover:
- handover-writer subagent creates YAML
HANDOVER.md - Confirm — do NOT spawn
- Remind: can run
/session-transfer:start-from-handoverlater
Choice 5: Log only
- Find Agent-Logs path (memory
reference_agent_logs.md, fall back~/repos/github/my-repos/Agent-Logs/) - If missing, suggest
/session-transfer:setup-agent-logs. Stop. - Write JSON log:
- Folder:
DDMMYY/, File:HHMMSS_model-name.json - Schema:
{"created":"ISO8601","model":"ID","agent_type":"Claude Code session","working_directory":"/path","repository":"name","branch":"name","last_commit":"hash msg","blocked":false,"user_input_needed":false,"debugging_required":false,"pending_tasks":0,"goal":"summary","completed":[],"in_progress":[],"not_started":[],"blockers":[],"resumption_summary":"next steps"} - Folder:
- Commit, push, run
python3 scripts/ingest.pyif exists - Report: "Session logged. No handover, no spawn."
Choice 6: Log + spawn (no handover)
- Write log (same as Choice 5)
konsole --workdir "$(git rev-parse --show-toplevel)" -e claude &- Report: "Logged + spawned. No handover — fresh session."
Choice 7: Clipboard handover
Run /session-transfer:clipboard-handover:
- Gather git state
- Compose short YAML summary from conversation + git state
- Display in chat as code block
- Copy via
wl-copy(fall backxclip) - Confirm: "Copied to clipboard."
- No files, no spawn
Notes
/handover quickor/handover 2skips menu, goes direct- Individual commands still work as shortcuts
- Missing Agent-Logs: suggest
/session-transfer:setup-agent-logs, don't fail silently
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

