Menú
Use when the user asks Guardian to delete exact files or directories through the safe path-deletion plan/apply flow.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | guardian-delete-paths |
| description | Use when the user asks Guardian to delete exact files or directories through the safe path-deletion plan/apply flow. |
Plan exact path deletion through the Guardian Codex adapter:
node <adapter-path> tool guardian_delete_paths '{"mode":"plan","paths":[...]}'
Inspect every approved target and blocker. Apply only after explicit delete confirmation with mode: "apply", confirmDelete: true, and the same path options. Use allowTracked or allowRecursive only when explicitly intended.
Do not run raw filesystem deletion, forced cleanup, worktree removal, branch deletion, hard reset, forced clean, stash mutation, or protected-branch bypasses.
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.