Menu
Use when the user asks Guardian to prune stale terminal, poisoned primary/protected, or orphaned session records.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 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.
| name | guardian-gc |
| description | Use when the user asks Guardian to prune stale terminal, poisoned primary/protected, or orphaned session records. |
Plan record-only state cleanup through the Guardian Codex adapter:
node <adapter-path> tool guardian_gc '{"mode":"plan"}'
Apply only after explicit confirmation with mode: "apply", confirmDelete: true, and the returned token posture handled by the adapter.
guardian_gc removes only Guardian JSON session records. It never deletes git branches, worktrees, refs, stashes, or files.