post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed to by {{CMD:cleanup}}.
npx skills add arbiterForge/codeArbiter --skill post-merge-cleanup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# post-merge-cleanup The walk back from a merged PR. Routed to by `{{CMD:cleanup}}`. The work has landed on the default branch. What is left is local: the branch you are standing on, and whatever the run left in the tree. This skill returns you to a clean, fast-forwarded default checkout without losing anything you have not explicitly agreed to lose. **It is ordinary lifecycle work and never needs `{{CMD:override}}`.** When it cannot proceed, it names the gate that stopped it. Issue #308 recorded the alternative: with no owner for this transition, the routing loop reached for `{{CMD:chore}}`, then for `{{CMD:override}}` — a bypass manufactured to cover a coverage hole. ## Pre-flight Read this, or STOP and surface the gap — never guess the default-branch name: - `{{PROJECT_DIR}}/.codearbiter/CONTEXT.md` — the default-branch name. If HEAD is already the default branch, there is no transition to make. Report the dirty state read-only and exit; branch pruning across *other* branches belongs to `{{CMD:standup}}`. ## Phase 1 — Prove the merge · gate: BLOCK A branch that looks merged is not merged. Establish it against the network, not against a stale local ref. This repo squash-merges by
- Pre-flight
- Phase 1 — Prove the merge · gate: BLOCK
- Phase 2 — Classify the residue · gate: BLOCK
- Phase 3 — Resolve the residue · gate: STOP
- Phase 4 — Transition · gate: BLOCK
- Phase 5 — Delete the merged local branch · gate: STOP
- Phase 6 — Receipt
- Hard rules
What does the post-merge-cleanup skill do?
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed to by {{CMD:cleanup}}.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill post-merge-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.