git:branch-cleanup

Git Branch Cleanup - Merged and Stale Branch Management

Clean up merged and stale branches locally and remotely with comprehensive safety checks.

Command

/git:branch-cleanup [scope] [base-branch]

Arguments

• $1: scope - local|remote|both (default: local)
• $2: base-branch - Branch to check merges against (default: main or master)

Description

Over time, repositories accumulate branches from completed features, merged pull requests, and abandoned work. Branch cleanup helps maintain repository hygiene by identifying and safely removing branches that are no longer needed, while protecting active and important branches.

Use Cases

• Clean up after merged pull requests
• Remove abandoned feature branches
• Prepare repository for new work
• Reduce clutter in branch listings
• Find stale branches that need attention
• Audit branch activity across team
• Free up branch names for reuse

Branch Categories

Branches are classified into categories:

1. Fully Merged - Safe to delete

   • All commits are in base branch
   • Feature complete and merged
   • No unique changes

2. Partially Merged - Review before delete

   • Some commits merged
   • May have additional work
   • Requires investigation

3. Stale - No activity for long period

   • No commits in 90+ days
   • May be abandoned
   • Should be reviewed before delete

4. Active - Recent activity

   • Commits within last 30 days
   • Likely still in use
   • Should not be deleted

5. Protected - Never delete

   • main, master, develop
   • production, staging
   • release branches
   • Explicitly configured protected branches

Workflow

Initial Analysis

1. Identify base branch:

   • Check for main or master
   • Use user-specified branch if provided
   • Validate base branch exists

2. Gather branch information:

   # List all branches
   git branch -a
   
   # For each branch, get:
   # - Last commit date
   # - Last author
   # - Commit count ahead/behind
   # - Merge status