メニュー
Resume work on a DIFFERENT surface (web, desktop, or CLI) from a tracked cross-surface handoff written by /handoff. Pulls the branch, reads the latest docs/handoffs/session-*.md, restates the plan, and continues. Invoke as /resume [handoff-file].
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Prepare for a /clear: bring all documentation up to date with this session's changes, persist recovery context (memory + handoff), and emit a copy-paste resume prompt so the next session begins the next task with zero context loss. Invoke explicitly as /clear-prep [next-task].
Use when adding or modifying a devcontainer feature in devcontainer.json - fetch its devcontainer-feature.json schema first and verify every option key exists, because features silently drop unknown options.
Use when creating branches, commits, pushes, or PRs with plain git. Branch BEFORE committing — never commit directly onto the default branch. Avoids virtual-branch composition bugs where commits silently depend on other applied branches.
Write a CROSS-SURFACE session handoff to a tracked path and push it, so a session on another surface (web, desktop, or CLI) can continue with zero context loss. Use when ending a session whose work must be picked up on a DIFFERENT machine/surface. For same-machine /clear continuity use /clear-prep instead. Invoke as /handoff [next-task].
Use when running parallel-scientist research - ALWAYS follow with an opus verification stage that re-probes load-bearing claims and surfaces gaps. Skipping the verifier almost shipped a wrong recommendation in session 2026-04-07e.
Use when sharing a single `~/.ssh/config` across macOS + Linux - apply OpenSSH `IgnoreUnknown` to tolerate macOS-only directives (`UseKeychain`, `AddKeysToAgent`) on Linux where they would otherwise be fatal.
| name | resume |
| description | Resume work on a DIFFERENT surface (web, desktop, or CLI) from a tracked cross-surface handoff written by /handoff. Pulls the branch, reads the latest docs/handoffs/session-*.md, restates the plan, and continues. Invoke as /resume [handoff-file]. |
| disable-model-invocation | true |
| argument-hint | [path to a specific handoff file, optional] |
The receiving side of /handoff. Reconstructs working context on a fresh
surface from the tracked handoff on the branch (Claude Code has no built-in
cross-device session resume — the branch is the only carrier). $ARGUMENTS
(optional) is a specific handoff file; if empty, use the most recent one.
Get the latest branch state so the handoff and the files it references are present locally:
git fetch origin
git checkout {branch} # the branch named in the handoff / PR
git pull --ff-only
If you don't yet know the branch, list recent handoffs after a plain
git fetch and pick the newest, or ask the user which PR/branch to resume.
Use $ARGUMENTS if given; else pick the newest
docs/handoffs/session-*.md (latest date, then latest letter suffix). Read
it in full — it is designed to be self-sufficient. Also open the preload
pointers it names (plan/spec/issue/PR) so you load the real working set, not
just the summary.
Before doing any work, confirm you reconstructed context correctly: state the branch/PR, what shipped, the next task, and any OPEN DECISIONS the handoff flagged as awaiting the user. This catches a stale or wrong handoff before it costs you.
If the handoff reports gates green, and you are on a surface where the gates run (desktop/CLI with the toolchain — NOT a bricked web session), optionally re-confirm before building on top:
mise run lint
uv run --project python pytest tests/ -x -q
dotfiles-setup verify run
Trust the real rc/conclusion, never a piped tail
(.claude/rules/verify-before-advancing.md).
Proceed with the next task from the handoff. If it was ambiguous, resolve it
with the user (AskUserQuestion) before acting
(.claude/rules/clarify-before-acting.md).
docs/handoffs/session-*.md read in full + preload pointers opened..claude/skills/handoff/SKILL.md — the sending side.docs/handoffs/README.md — the protocol + template..claude/rules/verify-before-advancing.md — trust the artifact, not a tail.