القائمة
Handoff the current conversation and open a new Claude instance in a fresh tmux window to continue the work. Use when the user wants to spin up a new agent session from the current one.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review the changes since a fixed point along three independent axes — Standards (does the code follow this repo's documented conventions and avoid known smells?), Spec (does it do what the issue/PRD asked?), and Architecture (does the change belong in the system and raise its evolvability — working with the grain of the existing seams, domain model, and layers to leave the architecture cheaper to change next — rather than lowering it?). Runs three parallel sub-agents that never share context and reports them side by side. The strongest architectural opportunity gets a concrete follow-up the operator can run. Use when the user wants to review a branch, a PR, or work-in-progress changes, or asks to "review since X".
Hand work to another agent through the mailbox — send to a named existing peer, or, when no name is given and the context calls for it, create a new agent wired to reply to you. Use when the operator says "dispatch to <name>" or "dispatch this to a new agent", optionally refining what to send.
Pure-filesystem inter-agent mailbox so any agent session can send a handoff document to another and pick up replies. Use when you need to set up your mailbox, send or reply to another agent, check for or wait on incoming messages, resolve another agent by name, take over / claim an existing mailbox identity (e.g. "take over Alice's mailbox"), or prune stale mailboxes from the registry. The fabric beneath the spawn, handback, and dispatch skills.
Return your work to the parent agent that spawned you by producing a handoff and sending it back through the mailbox. Use when you are a spawned/child session that has finished (or reached a checkpoint on) a side-quest and the operator wants the findings returned to the originating session.
Generate a markdown changelog for the changes between a fixed point and HEAD, enriched with issue-tracker context. Use when asked for a changelog, release notes, or a summary of merged work over a range or time window. Pass through whatever the user names as the base (SHA, branch, tag, main, HEAD~5, or a date window); detect the issue tracker from the repo's environment; follow Keep a Changelog headings; update an existing CHANGELOG.md in place when one is present.
Ruthless token-minimization mode plus a "token police" prompt check. Tokens are water; you are dying of thirst. Drops filler, prefers single words and emojis, answers yes/no with ✅/❌, and flags bloated user prompts. Use when user says "desert mode", "token police", "save tokens", "be ruthless", "stop wasting tokens", or invokes /desert-mode.
| name | spawn |
| description | Handoff the current conversation and open a new Claude instance in a fresh tmux window to continue the work. Use when the user wants to spin up a new agent session from the current one. |
| argument-hint | What will the next session be used for? |
| license | MIT |
| metadata | {"author":"William Duyck","version":"0.2"} |
Run /handoff (passing any user arguments through) to produce the handoff document.
Open it in a new tmux window using a 2–3 word kebab-case slug derived from the session's focus as the window name (e.g. auth-refactor, csv-parser), and the same agent CLI that invoked this skill.
For claude and codex, pass the handoff path directly:
tmux new-window -n "$TITLE" "$AGENT $HANDOFF_PATH"
For opencode, instead, start it with an initial prompt that tells it to read the handoff document:
tmux new-window -n "$TITLE" "$AGENT --prompt \"Read the handoff document at $HANDOFF_PATH and continue from it.\""
If tmux is unavailable, print the path and prompt the user to run it manually.