← ClaudeAtlas

handofflisted

Write a complete session state capture to a HANDOFF file, then instruct user to /compact or /clear. Use before switching machines, hitting context limits, or handing off to a future session. Handles single-project, multi-project, and multi-machine sessions explicitly.
HermeticOrmus/ormus-handoff · ★ 0 · AI & Automation · score 72
Install: claude install-skill HermeticOrmus/ormus-handoff
# /handoff — Session Handoff > Capture everything a fresh Claude session needs to continue this work without losing the thread. When invoked, perform the following steps in order. Do not ask for confirmation — just execute. --- ## Step 1: Gather Context Collect the following (use Bash/Git/TaskList tools as needed): 1. **CWD** — `pwd` to know where the session is rooted 2. **Project markers** — does CWD or any ancestor contain `.git`, `package.json`, `CLAUDE.md`, or similar? 3. **Remote machines touched** — scan the conversation for `ssh <host>` invocations. List every host that was SSH'd into. This is critical for multi-machine sessions. 4. **Files actually edited** — the absolute paths of every file the session wrote to (local AND remote like `host:~/path/...`) 5. **Git state** — only for the LOCAL CWD if it's a git repo (`git status --short` + `git log --oneline -5`). Do NOT try to git-status remote paths. 6. **Active tasks** — check TaskList tool for in_progress or pending items 7. **Session audit** — review the full conversation and identify: - What was being built / worked on - What is complete vs. in-progress vs. blocked - Key decisions made, errors hit, approaches tried - Next concrete action needed --- ## Step 2: Classify the session and pick the write location Use this decision tree EXPLICITLY. Do not guess. Print which path you took in the final output. ### Path A: Local single-project session **Trigger**: CWD is inside a project (has `.git` /