菜单
Use when the user wants to save session context. This is a human-facing session handoff entrypoint that preserves work state via vibe3 handoff, not an automated persistence workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to classify dirty changes, create serial commits, split work into one or more PRs, or publish the current flow without merging it.
Use when the user wants to resume work on an existing branch or flow. Reads context, executes the next step, reviews the result, and reports to the user before proceeding. Equivalent to superpowers:executing-plans, using vibe3 as the execution backend.
Use when you need an overview of the Vibe Center project, its implementations (vibe2 shell and vibe3 python), the available commands, and the standard development workflow. This is the meta-skill that orients any agent to the project.
Use when starting or switching to a new human-collaboration task. Confirm the target issue, bootstrap the corresponding dev/issue flow scene, and hand off to the chosen implementation workflow. Do not use for resuming an existing branch; use vibe-continue instead.
Use after `scripts/install.sh` to guide users through machine-level setup, dependency checks, Claude/Codex toolchain readiness, and core feature introduction. Interactive onboarding for new users. Delegates diagnostics to `vibe doctor` and `vibe keys check`. Do not use for project-level configuration (use vibe-project-check instead).
Use after `vibe init` to verify target-project configuration completeness, tool availability, and environment readiness. Interactively prompts user to fill missing items. Orchestrates existing commands without adding Python code. Supports cross-project vibe3 readiness verification (Phase 5-8). Do not use for system-level installation issues (use vibe-onboard instead).
| name | vibe-save |
| description | Use when the user wants to save session context. This is a human-facing session handoff entrypoint that preserves work state via vibe3 handoff, not an automated persistence workflow. |
该技能是人机协作的 session 保存入口，负责整理当前会话并写入 handoff。
vibe-save 只负责人机交互：
vibe3 handoff appendvibe-save 不承担的职责（由基础设施承接）：
这些恢复语义由 vibe3 handoff、vibe3 flow 等基础设施承接。
vibe-save 不等于自动状态同步：
vibe-save 只写入 handoff，不自动回写 flow/task 状态vibe-save 和 vibe-continue 共享以下恢复契约：
最小恢复现场（由 handoff 承接）：
恢复顺序（vibe-continue 负责）：
优先读取基础设施事实：
vibe3 flow show
vibe3 handoff show
必要时补充：
git status --short在写入前必须先审阅已有内容，并核对共享真源与现场事实。
若发现现有 handoff 与当前事实不一致，必须先修正，再退出。
使用 vibe3 handoff append 写入，至少覆盖：
Handoff 应优先回答"下个会话接手时需要知道什么"。
如果当前目录承载的 flow 已能识别当前 task：
next_step，必要时同步 status 或 pr_refvibe3 handoff append "[vibe-save] session save: <summary>" --actor vibe-save --kind milestone
如果当前目录尚未识别出当前 flow 对应的 task：
vibe3 handoff append 写入当前状态只有在本次会话产出了稳定的项目约束、长期适用的定义或反复复用的规则时，才使用 mcp-search / claude-mem 记录。
如果只是完成当前任务、记录 blockers 或保存下一步，不写记忆，更不默认创建新知识库。
摘要应说明：
vibe3 handoff show 可验证）mcp-search / claude-mem 记录稳定共识# Current Task
- task_id:
- title:
- status:
# Current Scene
- branch:
- flow:
- worktree:
- pr:
- dirty:
# Completed This Session
- ...
# Current Judgment
- ...
# Blockers
- ...
# Next Step
- ...
# Key Files
- ...
vibe-save 只负责人机交互，不定义恢复语义