ca-cleanup
Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
npx skills add arbiterForge/codeArbiter --skill ca-cleanup --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-cleanup — post-merge branch transition Your PR merged. You are still standing on the branch, with build output, worktree residue, and scratch files around you. This command owns the ordinary walk back: prove the branch actually landed, decide what the leftovers are, get to a clean fast-forwarded default checkout, and drop the merged local branch. It exists because nothing else owned it. `$ca-standup` is daily hygiene and deliberately never touches the current branch or the default one; `$ca-chore` takes docs, dependency bumps, and reverts. Issue #308 recorded what the gap produced: a routine cleanup routed to `$ca-chore`, which refused it, and then to `$ca-override` — a bypass invented to cover missing coverage. This is that coverage. ## Routes to The `post-merge-cleanup` skill (`${CLAUDE_PLUGIN_ROOT}/routines/post-merge-cleanup/SKILL.md`), which owns the containment proof, the artifact classification, and the per-item confirmations. ## When NOT to use - The branch has NOT merged yet → `$ca-pr` (`finishing-a-development-branch`) owns the terminal decision; come back here after it lands. - Daily start-of-day hygiene across *other* branches and worktrees → `$ca-standup`. - A re
- Routes to
- When NOT to use
- Hard gate
What does the ca-cleanup skill do?
Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-cleanup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.