菜单
Compact the current conversation into a handoff document for another agent to pick up.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill to rebase gh-stack branches and resolve conflicts. Replaces raw git rebase for stack workflows. Triggers: restack, rebase, rebase on main, branches out of date, resolve conflicts.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to push a gh-stack stack and create or update stacked pull requests. Replaces git push and gh pr create for stack workflows. Triggers: push, ship it, send this up, submit, update PRs, create PR, push stack, send PRs.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
| disable-model-invocation | true |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Keep content already captured in vault artifacts, commits, and diffs in its source of truth. Reference vault stems and local paths instead of duplicating it.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
