opencode-worktree-guardian

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.

Use when the user asks Guardian to delete exact files or directories through the safe path-deletion plan/apply flow.

Use when the user asks Guardian to delete a worktree, orphan branch, stale branch, or explicitly abandon unmerged Guardian work.

Use when the user explicitly asks for low-level Guardian finish behavior rather than the normal guardian-done workflow.

Use when the user asks Guardian to prune stale terminal, poisoned primary/protected, or orphaned session records.

Use when the user asks for the Guardian HUD, dashboard, or control-room view from Codex.

Use when the user asks Guardian to scan hygiene findings, review workspace residue, or plan/apply safe cleanup of approved findings.

Use when the user asks Guardian to preserve, keep, or mark current worktree work as terminal with a safety ref.

Use when the user asks Guardian to recover, inspect recovery refs, orphaned sessions, stashes, or suggested recovery evidence.

Use when the user asks Guardian to write or open an offline HTML report of sessions, worktrees, branches, risks, and recovery evidence.

Use when the user asks Guardian to start, create, attach, or repair a Guardian-owned worktree session.

Use when the user asks for Guardian status, worktree inventory, branch safety, stale sessions, or what Guardian sees now.

Use when Guardian finish is blocked and the user asks to plan or apply safe blocker resolution.