agentleFS
danielrosehilldanielrosehill/Claude-Hopper/skills/handover/SKILL.md

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

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.
  • steptianSkill

    harness-init

    初始化 .harness 开发框架,集成代码修改影响范围评估和测试覆盖建议功能。触发词:'初始化新项目'、'harness init'、'更新 harness'、'分析影响范围'、'评估修改影响'

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • GoogleSkill

    to-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

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • MicrosoftSkill

    caveman

    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

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
  1. Distinctive:

    Write minimal YAML HANDOVER.md

    line 49
  2. Very specific:

    Write JSON log to Agent-Logs (check memory for path, fall back ~/repos/github/my-repos/Agent-Logs/)

    line 56
  3. Very specific:

    Commit, push, run python3 scripts/ingest.py if exists

    line 57
  4. Very specific:

    If missing, suggest /session-transfer:setup-agent-logs.

    line 69
  5. Distinctive:

    Write log (same as Choice 5)

    line 80
  6. Distinctive:

    No files, no spawn

    line 91

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 spawn

2. 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:

  1. handover-writer subagent creates YAML HANDOVER.md
  2. Verify exists
  3. konsole --workdir "$(git rev-parse --show-toplevel)" -e claude "/session-transfer:start-from-handover" &
  4. Report

Choice 2: Quick handover + new session

Run /session-transfer:quick-handover:

  1. Capture git state
  2. Write minimal YAML HANDOVER.md
  3. Commit and push
  4. konsole --workdir "$(git rev-parse --show-toplevel)" -e claude "/session-transfer:start-from-handover" &
  5. Report

Choice 3: Log + full handover + new session

Run /session-transfer:log-and-handover:

  1. Write JSON log to Agent-Logs (check memory for path, fall back ~/repos/github/my-repos/Agent-Logs/)
  2. Commit, push, run python3 scripts/ingest.py if exists
  3. handover-writer subagent creates YAML HANDOVER.md
  4. Spawn + report

Choice 4: Write handover only

Run /session-transfer:write-handover:

  1. handover-writer subagent creates YAML HANDOVER.md
  2. Confirm — do NOT spawn
  3. Remind: can run /session-transfer:start-from-handover later

Choice 5: Log only

  1. Find Agent-Logs path (memory reference_agent_logs.md, fall back ~/repos/github/my-repos/Agent-Logs/)
  2. If missing, suggest /session-transfer:setup-agent-logs. Stop.
  3. 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"}
  4. Commit, push, run python3 scripts/ingest.py if exists
  5. Report: "Session logged. No handover, no spawn."

Choice 6: Log + spawn (no handover)

  1. Write log (same as Choice 5)
  2. konsole --workdir "$(git rev-parse --show-toplevel)" -e claude &
  3. Report: "Logged + spawned. No handover — fresh session."

Choice 7: Clipboard handover

Run /session-transfer:clipboard-handover:

  1. Gather git state
  2. Compose short YAML summary from conversation + git state
  3. Display in chat as code block
  4. Copy via wl-copy (fall back xclip)
  5. Confirm: "Copied to clipboard."
  6. No files, no spawn

Notes

  • /handover quick or /handover 2 skips menu, goes direct
  • Individual commands still work as shortcuts
  • Missing Agent-Logs: suggest /session-transfer:setup-agent-logs, don't fail silently

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.