一键导入
guardian-finish-workflow
Use when the user asks Guardian to plan or apply the implementation-done cleanup workflow for redundant merged worktrees and branches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user asks Guardian to plan or apply the implementation-done cleanup workflow for redundant merged worktrees and branches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | guardian-finish-workflow |
| description | Use when the user asks Guardian to plan or apply the implementation-done cleanup workflow for redundant merged worktrees and branches. |
Plan first through the Guardian Codex adapter:
node <adapter-path> tool guardian_finish_workflow '{"mode":"plan"}'
Inspect primary-worktree preflight, stash status, cleanup candidates, blockers, resolved base evidence, and the confirm token posture. Apply only after explicit user confirmation with mode: "apply", confirm: true, and the same options. A planned-partial token may authorize only the safe token-bound candidates it lists; candidate-level blockers and local base-sync divergence must remain reported after apply.
This workflow may remove only redundant merged Guardian worktrees and merged local branches through Guardian gates, plus token-bound merged remote Guardian refs from the resolved effective remote using expected-head leases. Local branch refs are deleted only after safety-ref creation, ancestry proof, and an exact expected-head check. It must not invent commits, merge protected branches, mutate stashes, force-delete branches, delete unproven local stale branches, or run raw cleanup.
Use when the user asks Codex to drive the repo to the configured Guardian desired end state, such as commit, land, push, clean Guardian worktrees/branches, and safe hygiene cleanup.
Use when the user asks Codex to run Guardian workflows such as guardian status, guardian done, guardian finish, guardian recover, or worktree cleanup. Routes through the Codex Guardian adapter instead of raw git cleanup commands.
Use when the user asks Guardian to initialize, bootstrap, or write the repo-local Guardian config.
Use when the user says Guardian done, finish the job, complete the implementation, land and clean up, or asks Codex to run the normal Guardian completion workflow.
Use when the user asks Guardian to inspect project roadmap, milestone, plan, or ULW execution evidence.
Use when the user asks Guardian to delete exact files or directories through the safe path-deletion plan/apply flow.