菜单
Use when the current human-collaboration flow has reached terminal PR state and the user wants to do final closeout. Confirm PR outcome, close owned issues, check for follow-up needs, delete resources, and switch back to main. Do not use for code changes or abandoned work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | vibe-done |
| description | Use when the current human-collaboration flow has reached terminal PR state and the user wants to do final closeout. Confirm PR outcome, close owned issues, check for follow-up needs, delete resources, and switch back to main. Do not use for code changes or abandoned work. |
PR 合并后的完整收口流程。
Use vibe-done for human-initiated manual cleanup after PR merge.
Use vibe-closeout only when Manager has written handoff indicate with cleanup instructions.
gh pr view <pr-number> --json state,mergedAt
/vibe-integrate检查当前 flow 负责的 issue 是否已关闭：
gh issue view <issue-number> --json state
判断是否需要创建 follow-up issue：
检查点：
若需要 follow-up：
gh issue create --title "Follow-up: <主题>" --body "来源: #<原 issue>, PR #<pr-number>"
只关闭当前 flow 负责的主 issue：
gh issue close <issue-number> --comment "已完成 in PR #<pr-number>"
不关闭关联 issue（由各自 flow 负责）。
删除本地和远程 branch：
# 删除本地 branch
git branch -D <branch-name>
# 删除远程 branch
git push origin --delete <branch-name>
删除当前 worktree（资源清理）：
# 先确认不在要删除的 worktree 中
pwd
# 删除 worktree
git worktree remove <worktree-path>
git checkout main
git pull origin main
根据当前环境记录终态：
判断环境：
# 检测是否有 flow 环境
vibe3 flow show
留痕规则：
有 flow 环境（正常情况）：使用 handoff 记录关闭决策
vibe3 handoff append "[vibe-done] flow closed" --actor vibe-done --kind milestone
无 flow 但有 issue：在 issue 中记录关闭决策
gh issue comment <issue-number> --body "## Flow Closed
**PR**: #<pr-number> (merged)
**Issues Closed**: <issue-links>
**Follow-up**: <issue-link or none>
**Resources Cleaned**: branch + worktree
**Completed At**: <ISO-8601>
"
都没有：无需留痕
留痕内容应包含：
完成后输出：
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).