Menu
Periodic maintenance sweep hub. Dispatches to /sweep-worktrees, /sweep-branches (and future /sweep-wip, /sweep-logs).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | sweep |
| description | Periodic maintenance sweep hub. Dispatches to /sweep-worktrees, /sweep-branches (and future /sweep-wip, /sweep-logs). |
| user-invocable | true |
| model | sonnet |
Hub skill for periodic maintenance sweeps. Dispatches to one or more sub-skills
that each reclaim a specific class of residual state. Default is dry-run; pass
--apply to actually delete.
SW-1. Invoke /sweep-worktrees (dry-run by default; pass --apply to delete).
SW-2. Invoke /sweep-branches (dry-run by default; pass --apply to delete).
SW-3. Invoke /sweep-plans (dry-run by default; pass --apply to delete).
SW-4. Future sub-skills to be added in subsequent PRs:
/sweep-wip — stale WIP fingerprints/sweep-logs — old terminal logs / temp filesForward --apply (and any other flags) to each invoked sub-skill verbatim.
--apply to actually delete..github/workflows/sweep.yml) and manual /sweep use this hub./sweep on the developer's machine, since CI runners do not
see local worktrees.--force — none of the sub-skills accept it by design.Conduct a decision-tree interview with the user to lock in requirements, motivation, scope, and non-goals before planning.
Stage 3 of three-stage planning pipeline. Produce a file-level implementation plan via detail-planner/detail-reviewer loop, then get user approval. Inputs are confirmed intent (<session-id>-intent.md) and outline (<session-id>-outline.md) from prior stages.
Edit source code for the current task. Delegates editing and lint/typecheck/self-repair to a subagent.
Plan and write test cases with high reasoning effort. Test iteration runs in a subagent to minimize confirmations.
Explore the codebase to understand existing patterns, constraints, and relevant files before planning.
Investigate git history, docs/history.md, and GitHub issue/PR timeline since the relevant issue opened, to surface changes that may invalidate the issue's premises.