菜单
Compact the current session into a handoff document a fresh agent can resume from. Use when the context is getting long, you are switching tasks, or you want to end a session and continue clean without losing the thread.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Deep code review of a diff across both Orbit repos against one shared rubric, orchestrating the five review subagents and a backward-compat guard. Use when the user asks to review a PR, file, folder, or staged changes in orbit-ui-mobile or orbit-api. Replaces /review and /security-review.
Get an independent cross-model second opinion (GLM-5.2 via opencode) on a specific, load-bearing technical claim or a Critical code-review finding — a different model reads the claim + code and returns AGREE / DISAGREE / UNSURE. Use to stress-test a single Critical finding, a risky assertion, or a close call before you commit to it. Auto-fired inside /pr-review on each Critical finding that survives the skeptic. Not for open-ended research (use /deep-research) or multi-lens judgement (use /llm-council).
Break a PRD into GitHub issues across orbit-ui-mobile + orbit-api
Answer an open-ended "what's the best way to…?" question with orchestrated multi-agent deep web research. Decompose the question, fan out narrow research subagents in parallel, verify the load-bearing claims adversarially, iterate to saturation, then synthesize ONE opinionated, source-backed, decision-ready recommendation. Orbit-aware (dual-repo stack, solo-dev cost calibration). Use for technology/vendor choices, architecture & tooling decisions, cost comparisons, migration approaches, or best-practice questions — anything whose answer needs current external evidence beyond the codebase. Not for code edits, single-fact lookups, or questions answerable from the repo alone.
Create implementation plan with cross-repo codebase analysis
Prime agent with Orbit project context (both repos + optional GitHub issue)
| name | handoff |
| description | Compact the current session into a handoff document a fresh agent can resume from. Use when the context is getting long, you are switching tasks, or you want to end a session and continue clean without losing the thread. |
| argument-hint | ["note about what the next session is for"] |
Input: $ARGUMENTS (optional note on what the next session should focus on)
Squeeze the current conversation down to its resumable core: a single document a fresh Claude (or opencode) session can read to pick up exactly where this one left off, without inheriting this session's bloated context.
.claude/plans/*.md, a PRD, an ADR, a commit, a diff, a PR) is linked by path or number, never pasted in..claude/, and any files mid-edit./implement, /pr-review) and any open question or risk..claude/handoffs/<kebab-topic>.md (create the dir if missing). Tailor the emphasis to $ARGUMENTS if given.# Handoff: <topic>
Written: <date> · Next session: <the $ARGUMENTS focus, or "continue">
## State
- Task: <one line>
- Branch(es): ui-mobile <branch> · api <branch> (if touched)
- PR(s): #<n> (<status>) · Issue: #<n>
## Done this session
- <decision / change, referencing files by path>
## Next steps
1. <concrete next action> — suggested: /<skill>
2. ...
## References (not copied)
- Plan: .claude/plans/<file>
- <other artifacts by path/URL>
## Open questions / risks
- <anything unresolved>
Keep it short. A good handoff is the conversation squeezed to just its resumable core.