GI

git-branch-cleanup

This skill identifies local Git branches by merge status and guides the user through secure deletion.

Install

mkdir -p .claude/skills/git-branch-cleanup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4017" && unzip -o skill.zip -d .claude/skills/git-branch-cleanup && rm skill.zip

Installs to .claude/skills/git-branch-cleanup

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Analyzes and safely cleans up local Git branches. Categorizes branches by merge status,
staleness, and remote tracking. Provides interactive selection with safety guards.
Use when the user wants to clean up branches, delete old branches, organize Git branches,
or asks about which branches can be safely deleted.
312 chars · catalog description✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • Analyze local Git branches for merge status and staleness
  • Categorize branches into safety levels for deletion
  • Display branches with their last commit date and upstream tracking
  • Identify branches that are merged to the base branch
  • Detect branches whose remote counterparts have been deleted
  • Remove associated worktrees before deleting branches

How it works

The skill collects Git branch information, categorizes branches by merge status, staleness, and remote tracking, and then prompts the user for deletion with safety checks.

Inputs & outputs

You give it
Local Git repository with multiple branches
You get back
Categorized list of branches and confirmation for deletion of selected branches

When to use git-branch-cleanup

  • Cleaning up merged branches after a PR
  • Deleting local branches that were deleted on remote
  • Finding and removing stale development branches
  • Organizing a cluttered local Git workspace

About this skill

Git Branch Cleanup

Safely organize and clean up local Git branches. Categorizes branches by merge status, staleness, and remote tracking, then guides users through safe deletion.

Contents

  • Quick Start
  • Workflow (Steps 1-5)
  • Commands Reference
  • Dry Run Mode
  • Safety Checklist

Quick Start

  1. Analyze branches (Step 1)
  2. Categorize by safety level (Step 2)
  3. Display results and ask user which to delete (Step 3)
  4. Verify against safety guards (Step 4)
  5. Execute deletion after confirmation (Step 5)

Workflow

Step 1: Branch Analysis

Collect information with these commands:

# Decide base branch (prefer auto-detect; fallback to main)
BASE_BRANCH="$(
  git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@'
)"
[ -n "$BASE_BRANCH" ] || BASE_BRANCH=main

# List all branches with last commit date
git for-each-ref --sort=-committerdate refs/heads/ \
  --format='%(refname:short)|%(committerdate:relative)|%(upstream:trackshort)|%(contents:subject)'

# Merged branches (against base)
git branch --merged "$BASE_BRANCH"

# Unmerged branches
git branch --no-merged "$BASE_BRANCH"

# Branches whose upstream is gone (remote deleted)
git branch -vv | grep -F ': gone]' || true

# List worktrees (branches with '+' prefix in git branch -v have worktrees)
git worktree list

# Branches with worktrees ('+' prefix indicates worktree association)
git branch -v | grep '^+' || true

# Branches ahead of upstream (have unpushed commits)
git for-each-ref refs/heads \
  --format='%(refname:short) %(upstream:trackshort)' \
  | grep '>' || true

Step 2: Categorization

Categorize branches by safety level:

CategoryDescriptionSafety
Merged (Safe)Already merged to base branchSafe to delete
Gone RemoteRemote branch deletedReview recommended
StaleNo commits for 30+ daysNeeds review
Has WorktreeBranch checked out in a worktree (+ prefix in git branch -v)Remove worktree first
Ahead of UpstreamHas unpushed commits⚠️ Do not delete
UnmergedActive work in progressUse caution

Note: 30 days is a reasonable default for stale detection. Adjust based on team's sprint cycle if needed (e.g., 14 days for 2-week sprints).

Step 3: Display Format

## Branch Analysis Results

### Safe to Delete (Merged)
  - feature/login (3 weeks ago) - Add login feature
  - fix/typo (2 months ago) - Fix typo in readme

### Remote Deleted
  - feature/old-api (1 month ago) - Remote branch no longer exists

### ⚠️ Ahead of Upstream (DO NOT DELETE)
  - feature/wip (1 day ago) - Has 3 unpushed commits

### Stale Branches (30+ days)
  - experiment/cache (2 months ago) - Unmerged

### Active (Unmerged)
  - feature/new-dashboard (2 days ago) - Work in progress

---
Which categories would you like to delete?
1. Merged only (safest)
2. Merged + remote deleted
3. Select individually

Step 4: Safety Guards

Never delete these branches:

  • main
  • master
  • trunk
  • develop
  • development
  • Currently checked out branch

Always confirm before deletion:

The following branches will be deleted:
  - feature/login
  - fix/typo

Continue? (y/N)

Step 5: Execute Deletion

# After confirmation
git branch -d <branch-name>  # For merged branches
git branch -D <branch-name>  # Force delete (unmerged)

For branches with worktrees, remove the worktree first:

# Check if branch has a worktree
git worktree list | grep "\\[$branch\\]"

# Remove worktree before deleting branch
git worktree remove --force /path/to/worktree
git branch -D <branch-name>

Bulk delete [gone] branches with worktree handling:

# Process all [gone] branches, handling worktrees automatically
git branch -v | grep '\[gone\]' | sed 's/^[+* ]//' | awk '{print $1}' | while read branch; do
  echo "Processing branch: $branch"
  # Find and remove worktree if it exists
  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
  # Delete the branch
  echo "  Deleting branch: $branch"
  git branch -D "$branch"
done

Commands Reference

# Bulk delete merged branches (excluding protected branches and current branch)
# Notes:
# - Uses for loop + case for bash/zsh compatibility (avoids `while IFS= read` issues in zsh).
# - Uses case statement for exact-name matching (avoids grep regex edge cases).
# - Always exclude the current branch to prevent accidental self-deletion.
BASE_BRANCH="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@')"
[ -n "$BASE_BRANCH" ] || BASE_BRANCH=main
CURRENT_BRANCH="$(git branch --show-current)"
for branch in $(git branch --merged "$BASE_BRANCH" | sed 's/^[* ]*//'); do
  case "$branch" in
    main|master|trunk|develop|development|"$CURRENT_BRANCH"|"") continue ;;
    *) git branch -d "$branch" ;;
  esac
done

# Prune remote-tracking references (requires network access)
# Note: This may fail if offline or remote is unreachable.
# If it fails, skip this step - branch analysis still works with cached remote data.
git fetch --prune || echo "Warning: Could not reach remote. Using cached data."

# List oldest branches (30+ days)
git for-each-ref --sort=committerdate refs/heads/ \
  --format='%(committerdate:short) %(refname:short)' | head -20

# Worktree commands
git worktree list                              # List all worktrees
git worktree remove /path/to/worktree          # Remove a worktree
git worktree remove --force /path/to/worktree  # Force remove (even if dirty)
git worktree prune                             # Clean up stale worktree refs

Dry Run Mode

Preview deletions without executing:

# Preview only
BASE_BRANCH="$(git symbolic-ref --quiet --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@')"
[ -n "$BASE_BRANCH" ] || BASE_BRANCH=main
CURRENT_BRANCH="$(git branch --show-current)"
for branch in $(git branch --merged "$BASE_BRANCH" | sed 's/^[* ]*//'); do
  case "$branch" in
    main|master|trunk|develop|development|"$CURRENT_BRANCH"|"") ;;
    *) echo "$branch" ;;
  esac
done

Trigger dry-run mode if user says "--dry-run", "preview", or "just show me".

Safety Checklist

Before deletion, verify:

  • Not the current branch
  • Not a protected branch (base/main/master/trunk/develop)
  • No unpushed commits (ahead of upstream)
  • Worktree removed first (if branch has associated worktree)
  • User confirmation obtained

Quick safety commands

# Show "ahead/behind" vs upstream for each local branch
git for-each-ref refs/heads \
  --format='%(refname:short)|%(upstream:short)|%(upstream:trackshort)|%(committerdate:relative)|%(contents:subject)' \
  --sort=-committerdate

# For a specific branch, confirm it's not ahead of upstream (if upstream exists)
# (Empty output => nothing unpushed)
git log --oneline @{u}..HEAD 2>/dev/null || echo "No upstream configured for this branch"

# Check if a branch has an associated worktree
# ('+' prefix in git branch -v output indicates worktree)
git branch -v | grep "^+" | awk '{print $2}'

# Find worktree path for a specific branch
git worktree list | grep "\\[branch-name\\]"

When not to use it

  • When the user needs to delete the currently checked out branch
  • When the user needs to delete protected branches like 'main' or 'master'
  • When the user needs to delete branches with unpushed commits

Prerequisites

git 2.17+git 2.22+

Limitations

  • Cannot delete the currently checked out branch
  • Cannot delete protected branches (main, master, trunk, develop, development)
  • Cannot delete branches with unpushed commits

How it compares

This skill automates the analysis and interactive deletion of Git branches with built-in safety guards, unlike manual Git commands that require individual checks.

Compared to similar skills

git-branch-cleanup side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git-branch-cleanup (this skill)17moReviewBeginner
resolve-conflicts818moReviewIntermediate
openspec-onboard106moReviewBeginner
codex-cli-bridge99moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry