skills/vibe-done/SKILL.md
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.
npx skillsauth add jacobcy/vibe-coding-control-center vibe-doneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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 的 handoff 链中记录终态:
vibe3 handoff append "vibe-done: flow closed" --actor vibe-done --kind note
格式:
## Flow Closure
- flow: <flow-name>
- status: completed
- pr: <pr-link> (merged)
- issues_closed: <issue-links>
- follow_up: <issue-link or none>
- resources_cleaned: branch + worktree
- completed_at: <ISO-8601>
完成后输出:
development
Use after `vibe init` to verify project configuration completeness. Interactively prompts user to fill missing items. Orchestrates existing commands without adding Python code. Do not use for system-level installation issues (use vibe-onboard instead).
development
Use when the user wants a comprehensive review using the multi-agent team workflow. Applies to PRs, code changes, architecture decisions, and any task requiring team-based analysis.
development
Use when manager has signaled flow terminal state cleanup via handoff indicate. Reads cleanup instructions and executes FlowCleanupService. Do not use for code changes or PR creation.
testing
Use for handling blocked and RFC issues, making decisions that may form ADRs (Architecture Decision Records). Processes problem issues requiring human judgment, dependency resolution, and architectural decisions. Do not use for routine issue monitoring (use vibe-orchestra) or roadmap planning (use vibe-roadmap).