What problem does it solve? After finishing a chunk of work, repositories accumulate merged feature branches, stale worktrees, unpushed commits, and stray edits. Cleaning them up by hand is error-prone — deleting the wrong branch destroys parallel work, while squash merges make merged branches look unmerged. This Skill brings a repository to a clean, on-main, synced state without losing anyone's work. ## Core Features & Use Cases - Read-only survey first: A bundled script snapshots branches, worktrees, stashes, PRs, and merge state before anything is touched, including patch-equivalence detection for squash-merged branches. - Explicit classification: Every branch and worktree is labeled integrate, delete, keep, or investigate with evidence, so parallel work and open PRs are never deleted by mistake. - Safe execution order: Commits, pushes, merges via GitHub PR squash or local fast-forward, syncs main with origin, then deletes approved branches and worktrees using reversible commands only. - Use Case: After a PR is merged, ask the assistant to tidy up — it commits remaining changes, merges the branch, returns the root worktree to main, deletes the merged branch locally and remotely, and reports a clean tree. ## Quick Start Ask the assistant to clean up the repository now that the current branch's work is finished and merged.