Skip to content

samuelpatro/.claude / skills/prune-branches

prune-branches

Verified

Cleans up local git branches marked as [gone] (deleted on the remote but still present locally), including removing any associated worktrees. Use when the user says "prune branches", "clean up gone branches", "/prune-branches", or asks to delete stale local branches whose remotes are gone.

Your task

Delete every local branch whose upstream is gone, removing any attached worktree first. If nothing is marked [gone], report that and stop.

Steps

  1. List branches with verbose status to surface [gone] markers and any + prefix indicating an attached worktree:

    git branch -v
    
  2. List worktrees so you know which paths will be removed:

    git worktree list
    
  3. Remove worktrees and delete [gone] branches in one pass. Strips the +/*/space prefix, finds the worktree (if any), and force-deletes the branch:

    git branch -v | grep '\[gone\]' | sed 's/^[+* ]//' | awk '{print $1}' | while read branch; do
      echo "Processing branch: $branch"
      worktree=$(git worktree list | grep "\\[$branch\\]" | awk '{print $1}')
      if [ ! -z "$worktree" ] && [ "$worktree" != "$(git rev-parse --show-toplevel)" ]; then
        echo "  Removing worktree: $worktree"
        git worktree remove --force "$worktree"
      fi
      echo "  Deleting branch: $branch"
      git branch -D "$branch"
    done
    

Reporting

  • Print which worktrees were removed and which branches were deleted.
  • If no [gone] branches exist, say "No cleanup needed" and stop.
  • Never delete branches that are not marked [gone].
  • Never touch the current working tree's root path.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall