Clean Branches
$ npx claude-code-templates@latest --command="utilities/clean-branches" --yesRequires Claude Code. The command adds this command to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this command
Component source
Clean Branches Command
Clean up merged and stale git branches
Instructions
Follow this systematic approach to clean up git branches: $ARGUMENTS
- Repository State Analysis
- List all local and remote branches
- Identify the main/master branch name
- Review recent branch activity and merge history
# Check current status
git status
git branch -a
git remote -v
# Check main branch name
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'
- Safety Precautions
- Switch to main/master branch
- Pull latest changes from remote
- Create backup of current branch state if needed
# Ensure clean state
git stash push -m "Backup before branch cleanup"
git checkout main # or master
git pull origin main
- Identify Merged Branches
- Exclude protected branches (main, master, develop)
- Check both local and remote merged branches
- Verify merge status to avoid accidental deletion
# List merged local branches
git branch --merged main | grep -v "main\\|master\\|develop\\|\\*"
# List merged remote branches
git branch -r --merged main | grep -v "main\\|master\\|develop\\|HEAD"
- Identify Stale Branches
- Check last commit date for each branch
- Identify branches older than specified timeframe (e.g., 30 days)
- Consider branch naming patterns for feature/hotfix branches
# List branches by last commit date
git for-each-ref --format='%(committerdate) %(authorname) %(refname)' --sort=committerdate refs/heads
# Find branches older than 30 days
git for-each-ref --format='%(refname:short) %(committerdate)' refs/heads | awk '$2 < "'$(date -d '30 days ago' '+%Y-%m-%d')'"'
- Interactive Branch Review
- Check if branch has unmerged changes
- Verify branch purpose and status
- Ask for confirmation before deletion
# Check for unmerged changes
git log main..branch-name --oneline
# Show branch information
git show-branch branch-name main
- Protected Branch Configuration
- Configure protection rules for important branches
- Document branch protection policies
- Set up automated protection for new repositories
# Example protected branches
PROTECTED_BRANCHES=("main" "master" "develop" "staging" "production")
- Local Branch Cleanup
- Remove stale feature branches
- Clean up tracking branches for deleted remotes
- Update local branch references
# Delete merged branches (interactive)
git branch --merged main | grep -v "main\\|master\\|develop\\|\\*" | xargs -n 1 -p git branch -d
# Force delete if needed (use with caution)
git branch -D branch-name
- Remote Branch Cleanup
- Clean up remote tracking references
- Delete obsolete remote branches
- Update remote branch information
# Prune remote tracking branches
git remote prune origin
# Delete remote branch
git push origin --delete branch-name
# Remove local tracking of deleted remote branches
git branch -dr origin/branch-name
- Automated Cleanup Script
#!/bin/bash
# Git branch cleanup script
set -e
# Configuration
MAIN_BRANCH="main"
PROTECTED_BRANCHES=("main" "master" "develop" "staging" "production")
STALE_DAYS=30
# Functions
is_protected() {
local branch=$1
for protected in "${PROTECTED_BRANCHES[@]}"; do
if [[ "$branch" == "$protected" ]]; then
return 0
fi
done
return 1
}
# Switch to main branch
git checkout $MAIN_BRANCH
git pull origin $MAIN_BRANCH
# Clean up merged branches
echo "Cleaning up merged branches..."
merged_branches=$(git branch --merged $MAIN_BRANCH | grep -v "\\*\\|$MAIN_BRANCH")
for branch in $merged_branches; do
if ! is_protected "$branch"; then
echo "Deleting merged branch: $branch"
git branch -d "$branch"
fi
done
# Prune remote tracking branches
echo "Pruning remote tracking branches..."
git remote prune origin
echo "Branch cleanup completed!"
- Team Coordination
- Check if branches are being used by others
- Coordinate branch cleanup schedules
- Document branch cleanup procedures
- Branch Naming Convention Cleanup
- Clean up temporary or experimental branches
- Remove old hotfix and feature branches
- Enforce consistent naming conventions
- Verification and Validation
- Check that no active work was deleted
- Validate remote branch synchronization
- Confirm team members have no issues
# Verify cleanup results
git branch -a
git remote show origin
- Documentation and Reporting
- Report any issues or conflicts found
- Update team documentation about branch lifecycle
- Create branch cleanup schedule and policies
- Rollback Procedures
- Use reflog to find deleted branch commits
- Create emergency recovery procedures
- Set up branch restoration scripts
# Recover deleted branch using reflog
git reflog --no-merges --since="2 weeks ago"
git checkout -b recovered-branch commit-hash
- Automation Setup
- Configure CI/CD pipeline for branch cleanup
- Create scheduled cleanup jobs
- Implement branch lifecycle policies
- Best Practices Implementation
- Set up automated merge detection
- Configure branch protection rules
- Implement code review requirements
Advanced Cleanup Options:# Clean up all merged branches except protected ones
git branch --merged main | grep -E "^ (feature|hotfix|bugfix)/" | xargs -n 1 git branch -d
# Interactive cleanup with confirmation
git branch --merged main | grep -v "main\|master\|develop" | xargs -n 1 -p git branch -d
# Batch delete remote branches
git branch -r --merged main | grep origin | grep -v "main\|master\|develop\|HEAD" | cut -d/ -f2- | xargs -n 1 git push origin --delete
# Clean up branches older than specific date
git for-each-ref --format='%(refname:short) %(committerdate:short)' refs/heads | awk '$2 < "2023-01-01"' | cut -d' ' -f1 | xargs -n 1 git branch -D
Remember to:
- Always backup important branches before cleanup
- Coordinate with team members before deleting shared branches
- Test cleanup scripts in a safe environment first
- Document all cleanup procedures and policies
- Set up regular cleanup schedules to prevent accumulation
Related Claude Code Commands
Ultra Think
Multi-framework structured analysis: surfaces hidden assumptions, generates competing solutions, stress-tests each with adversarial reasoning, and delivers confidence-calibrated recommendations
Code Review
Comprehensive code quality review with security, performance, and architecture analysis
Refactor Code
A ready-to-install Claude Code component.
Explain Code
A ready-to-install Claude Code component.
All Tools
A ready-to-install Claude Code component.
Debug Error
A ready-to-install Claude Code component.
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.