cleanup

Goal

Dispatch to the target skill based on the cleanup domain — the parent only routes

Scope

• The argument is the domain; if not provided → /ask-me picks the domain

Execute

Skills

Domain	Skill
artifact	/cleanup-artifact — build artifacts + dependency caches (Rust CLI, dry-run first)
branches-merged	/cleanup-branches-merged — local branches already merged
docker	/cleanup-docker — unused images, containers, volumes
git-branch	/cleanup-git-branch — stale/orphan branches
github-issue	/cleanup-github-issue — old or resolved issues
worktree	/cleanup-worktree — unused git worktrees

1. Identify the domain from the argument (e.g. /cleanup-worktree)
2. If the domain is supported → follow the /cleanup-<domain> flow end to end
3. If no domain is given or it is unknown → /ask-me picks the domain

Rules

• The parent only dispatches — never duplicate the target skill's workflow

• Every cleanup must dry run + user confirm before actually deleting (per the target skill's rule)

• Use /cleanup-files-in-project if needed

• Use /cleanup-files-in-computer if needed

• Use /run-cleanup if needed

Expected Outcome

• The caller is dispatched to the target skill matching the domain, then cleans up following that flow