Repository Cleanup

Goal

Inspect local and remote branches, pull requests, commits, stashes, worktrees, and the local databases left behind by old worktrees. Recover valuable work, then remove the proven stale state the user selects, until the repository is current and organized. Nothing is removed that the user did not select by name.

Loop Prompt

Inspect local and remote branches, pull requests, commits, stashes, and worktrees. Recover valuable work, list everything stale, and remove only the items the user selects, until the repository is current and organized.

Stop when valuable work is recovered and remaining repository state is intentional.

When To Use

Use this when abandoned branches, old worktrees, unclear pull requests, unmerged commits, or forgotten stashes make it difficult to know which repository state still matters.

This loop cleans Git repository state. It is not a source-code housekeeping pass; use housekeeper for dead code, stale files, duplicated logic, broken links, unused dependencies, and project-structure cleanup.

Workflow

1. Inspect the current working tree before changing anything: current branch, uncommitted changes, stashes, remotes, upstreams, and registered worktrees.
2. Fetch current remote state without pruning. List the stale remote-tracking refs instead (git remote prune --dry-run <remote>); they are removal candidates like any other.
3. Inventory local branches, remote branches, open and recently closed pull requests, unmerged commits, stashes, worktrees, orphaned databases (see Databases), and old pr-assets folders (see PR screenshots).
4. Classify each item as current, valuable but unfinished, superseded, merged, abandoned, or uncertain.
5. Record evidence for each classification: upstream status, merge base, PR state, commit reachability, stash contents, worktree dirtiness, owner, and recent activity.
6. Recover valuable work before cleanup. Move useful commits or stashed changes to the appropriate current branch, preserve patches, or keep a clearly named branch.
7. Ask before removing anything. Show every removal candidate of the batch (merged branches, stale remote-tracking refs, stashes, worktrees, databases, remote branches, PRs to close) in one message: each item's exact name, the step 5 evidence, its size where known, and cannot recover when nothing else holds a copy. Then ask the user to pick what to remove, in the shape of Selection Form below. An answer that names no item ("ok", "go ahead") picks nothing.
8. Remove only the selected items, by their exact names. Everything unselected stays, and the report names it.
9. Rerun the inventory after cleanup until every remaining branch, pull request, commit, stash, worktree, and database is intentional.

Selection Form

Where AskUserQuestion is available, ask the step 7 selection in one call, one question (one tab) per kind of state, with up to 4 questions:

Leave out a tab with no candidates. Every question is multiSelect: true, asks "Which <kind> should I remove?", and has 2–4 options with nothing pre-ticked:

• One option is one batch of items of the same kind with the same evidence, such as "Merged branches (7)". The label says what the batch is, in 1–5 words. The description gives the exact command and every exact name it covers, so a pick selects those names and nothing else: "git branch -d feat/login, fix/typo, … (all merged into main)".
• Never batch a cannot recover item, an uncertain item, or a database with anything unlike it. Give it its own option, and say cannot recover in the description.
• Too many batches for 4 options: ask the rest in the next round, after this batch is removed and re-inventoried.

Without the tool, show the same tabs as numbered lists in chat, and take the numbers the user answers with.

Inventory Commands

Use the repository's existing tools and hosting provider first. Common Git and GitHub CLI checks:

git status --short --branch
git stash list
git stash show --stat stash@{0}
git remote -v
git fetch --all --no-prune --no-prune-tags
git remote prune --dry-run origin
git worktree list --porcelain
git branch --format='%(refname:short) %(upstream:short) %(committerdate:relative)'
git branch --merged
git branch --no-merged
git log --all --decorate --oneline --graph --date-order -n 80
gh pr list --state open --json number,title,headRefName,baseRefName,author,updatedAt,url
gh pr list --state closed --limit 30 --json number,title,headRefName,baseRefName,author,updatedAt,closedAt,mergedAt,url

Fetch with --no-prune --no-prune-tags even when the user's config sets fetch.prune or fetch.pruneTags: a pruning fetch deletes stale remote-tracking refs and local-only tags (an archive/* tag made to preserve work) that nobody selected. git remote prune --dry-run shows the stale refs as candidates instead.

Worktrees whose PR merged, and the databases left behind, come from one script. With no arguments it changes nothing and prints the candidates as JSON. It removes only the names you pass, after the user selected them, and it refuses the whole run, changing nothing, if one name is not a candidate:

bash scripts/prune-merged-worktrees.sh    # list: merged clean worktrees, their databases, orphans
bash scripts/prune-merged-worktrees.sh --remove <worktree path> --drop pgsql:<database>   # selected items only

A worktree's database can be dropped only in the same run that removes that worktree. Never pass a name the user did not select, and never build the arguments from the whole list.

If gh is unavailable or the repository is not on GitHub, use the equivalent provider CLI, web UI, or local Git evidence and report the PR visibility gap.

Databases

Worktrees and one-off test runs leave local databases behind: a per-worktree DB_DATABASE, throwaway test databases (<app>_pr42, <app>_triage_<date>), and Laravel parallel testing's <db>_test_N copies of each. The script's databases list holds, with sizes, each candidate database by exact name, a parallel-testing copy as an item of its own. Its source says why: worktree (registered for, or named by, a candidate worktree), registry (a registered database whose worktree is gone), or orphan (named <app db>_* and named by no .env, .env.testing, or phpunit.xml of the main checkout or a remaining worktree). It never lists a database in use, or a parallel-testing copy of one.

Classify each listed database by its name: a PR number, branch, worktree, or date that maps to merged or removed work is abandoned; a name that reads as a deliberate copy (_backup, _snapshot, _pre_migration) or maps to nothing is uncertain. Show the list grouped that way, with sizes, in the step 7 selection, and drop only the selected names, through the script's --drop. Each drop is irreversible: offer a pg_dump/mysqldump first for anything uncertain.

PR screenshots

The pr skill uploads PR screenshots to the orphan pr-assets branch, one folder per PR branch, and nothing else ever removes them: every clone downloads the whole branch. One script lists the folders whose PR merged or closed more than 90 days ago (--days N to change it), or, with no PR found, whose last upload is that old. An open PR's folder is never a candidate. With no arguments it changes nothing:

bash scripts/prune-pr-assets.sh                                        # plan: tip, candidates, kept, with sizes
bash scripts/prune-pr-assets.sh --tip <plan tip> --drop <folder>...    # selected folders only

Offer the candidates as one Remote option, with their count, total size and folder names, and cannot recover in its description: dropping rewrites pr-assets as a fresh orphan commit with a force push, leased on the plan's tip, so those images leave every future clone. A kept folder's …/blob/pr-assets/… links keep working; links pinned to a commit (…/blob/<sha>/…, from older uploads) point at unreachable commits that GitHub may stop serving once it garbage-collects them. A tip that moved since the plan refuses the run; list again.

Classification Guide

• Current: actively used branch, active pull request, current worktree, release branch, or protected branch.
• Valuable but unfinished: contains unmerged commits, unpushed commits, or stashed changes that appear relevant, even if old.
• Superseded: replaced by a newer branch, merged through a different branch, or made irrelevant by a later implementation.
• Merged: fully integrated into the target branch or corresponding pull request is merged.
• Abandoned: old, ownerless, no useful unique commits or stash contents, no active pull request, and no dirty worktree.
• Uncertain: insufficient evidence, unclear ownership, dirty worktree, ambiguous unmerged commits, unclear stash contents, or possible external dependency.

Uncertain items are not cleanup candidates until more evidence or user approval resolves them.

Cleanup Rules

• Every removal is one the user selected by name in step 7. Proof that an item is stale makes it a candidate, never a removal; no repository policy or earlier approval replaces the selection.
• Use git branch -d for selected local branches proven merged. Use git branch -D only after explicit approval and only after preserving any useful commits.
• Do not drop stashes until their contents have been inspected and the user has approved the exact stash to drop.
• Before removing a worktree, verify it has no uncommitted changes and its branch/commits have been classified.
• Drop a database only when the user selected that exact name. Never drop one the main checkout or a remaining worktree uses.
• Before deleting a branch with unique commits, preserve the work by merging, cherry-picking, tagging, renaming, or exporting patches.
• A preserving tag is local until pushed, so no later command in the run may prune tags. Confirm it exists (git rev-parse -q --verify refs/tags/<tag>) before deleting the branch it preserves.
• Before dropping a valuable stash, recover it onto the appropriate branch or preserve it as a patch with enough context to reapply.
• Prefer small batches. Re-inventory after each batch so the next decision uses current evidence.

Report

End with:

• Repository state inventoried.
• Branches, pull requests, commits, stashes, worktrees, and databases classified.
• Valuable work recovered or preserved.
• Cleanup actions taken, with evidence for each.
• Verification commands run after cleanup.
• Remaining intentional repository state, including any kept stashes.
• Deferred or uncertain items and what approval or evidence is needed.

Start each item that needs the user (a risk, a deferral, an approval) with ⚠️, and each failed check with ❌. No other marks.

Guardrails

• Do not discard uncommitted changes, stashes, unpushed commits, or dirty worktrees.
• Do not use git reset --hard, git checkout --, git clean, or force-delete branches unless the user explicitly asked for that exact destructive action.
• Do not close someone else's pull request or delete a remote branch without confirmation.
• Do not treat old age alone as proof that work is stale.
• Preserve evidence for every destructive cleanup action.