메뉴
Use when the user asks Guardian to prune stale terminal, poisoned primary/protected, or orphaned session records.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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.
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.