cleanup-merged-branches

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Delete remote branches whose PR was merged. Read-only dry-run, then confirm, then delete.

20installs

Sourcetimschoch/skilly

Added on2026-09-02

NPX Install

npx skill4agent add timschoch/skilly cleanup-merged-branches

SKILL.md Content

View Translation Comparison →

Delete remote branches that belong to a merged PR. Destructive, so it runs as a dry-run first and never deletes without explicit confirmation.

Delete rule

A branch is deletable iff all hold — encoded in

scripts/plan.sh

, the single source of truth:

it still exists on the remote,
it has a merged PR,
it has no open PR,
it is not protected.

Protected = the default branch +

staging

. Never delete these, even if a merged PR points at them. A branch with no PR, or only a closed-unmerged PR, is not deletable (it never "belongs to a merged PR"). Extend the protected set in

is_protected()

inside

scripts/plan.sh

, nowhere else.

Steps

Dry-run. Run
```
bash scripts/plan.sh
```
(pass a remote name as
```
$1
```
if not
```
origin
```
). It prints deletable branches as
```
<branch>  #<pr>  <title>
```
, and deletes nothing. Done when you have the list. Empty output → report "nothing to clean up" and stop.
Show + confirm. Show the full list to the user and ask for explicit go. Do not delete on a vague reply — only on a clear yes. This gate is mandatory every run.
Delete. For each confirmed branch:
```
git push origin --delete <branch>
```
. Nothing outside the plan's list may be deleted.
Report. List what was deleted; note any push that failed.

Also: stale-open issues

Closes #N

only auto-closes on merge into the default branch — a PR merged into an integration branch (e.g.

rebuild/v1

) leaves #N open forever. For each merged PR you clean up here, check its linked issue: if the work is on the default branch but the issue is still open, hand-close it (

gh issue close #N --reason completed --comment "merged via #<pr>"

). Same misfire hides "done" issues as open — this is where to catch them.