القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 asks Guardian to plan or apply the implementation-done cleanup workflow for redundant merged worktrees and branches.
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.
| name | guardian-done |
| description | 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 the Guardian Codex adapter for the implementation-done workflow:
node <adapter-path> tool guardian_done '{"mode":"plan"}'
Inspect the selected lane, dirty files, blockers, and cleanup preview. If the user invoked this completion workflow and the plan is safe, continue with the same plan options plus confirm: true; the adapter reuses the matching plan token. Include an explicit commitMessage when Guardian needs to commit dirty work. Add allowAdminBypass: true only when the user explicitly approves a branch-protection bypass for that run.
guardian_done resolves the target from repo-wide inventory, not from whichever cwd Codex happens to be in. Bare guardian_done auto-selects exactly one dirty implementation target. If multiple dirty targets exist, stop on needs-selection and rerun the exact primary=true, sessionId=..., or branch=... option shown in the output. Use explicit primary=true, sessionId=..., or branch=... from any cwd when the user already selected the target.
Never replace guardian_done with raw push, merge, branch deletion, worktree deletion, stash mutation, force-push, or protected-branch bypass commands.