菜单
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.
用 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.
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.
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 | handback |
| description | 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. |
| argument-hint | What are you handing back? |
| license | MIT |
| metadata | {"author":"William Duyck","version":"0.2"} |
The mailbox reply flow with the recipient fixed to your parent — the from
of your message-zero, the bootstrap handoff you drained on launch.
Find your message-zero — the message whose subject begins spawn:, in your
archive/ (or inbox/ if still unread):
zero="$(grep -rlE '^subject: spawn:' "$(mb_dir "$(mb_resolve_self)")"/{archive,inbox} 2>/dev/null | head -1)"
Run the mailbox reply flow against $zero — compose the return body per the
mailbox compose rules and stream it in. It sends home, threaded to your
parent. Confirm to the operator what was sent and to whom (mb_whois for the
parent's friendly name).
If there is no spawn: message-zero you were not created with a return channel, so
there is no parent — use dispatch to send to a named peer instead.
If your handoff asks the parent to do any further mailbox work, name the flow
("check your inbox", "reply to thread back"), never the mb_* engine functions
— the flow doc carries the discipline a bare function name would leave behind.