cleanup-git

To clean up stale local git branches, this Skill identifies local branches whose remote tracking references have been deleted and guides you through selecting and confirming which ones to delete. It skips the main and currently checked-out branches for safety.

Yes, you can safely delete merged git worktrees. This Skill detects worktrees on branches merged into main, avoids those with uncommitted changes, and requires explicit confirmation before deletion to ensure no unsaved work is lost.

The best way to prune stale git branches and worktrees safely is using a cleanup process that detects uncommitted changes and skips those worktrees. This Skill automatically skips worktrees with uncommitted changes, protecting the currently checked-out branch and the main branch.

Branch cleanup automation handles the main branch and currently checked-out worktrees by skipping them entirely. This prevents accidental deletion of active work, ensuring only stale local branches and worktrees with merged remote references are presented for deletion.

No, this git branch cleanup tool does not require any dependencies or components to run. It operates independently to identify stale local branches and worktrees, guiding you through selection and confirmation before deletion.

You should remove stale local branches and worktrees to reduce repository clutter and confusion. Cleaning up branches that have already been merged remotely keeps your local development environment organized and prevents accidental commits to outdated work.