git-cleanup

To safely clean up local Git branches after a squash merge, the workflow analyzes PR evidence to classify them and uses a gated confirmation process before executing a force delete (git branch -D). This ensures squash-merged branches are removed without losing uncommitted work.

The best way to delete accumulated Git worktrees without losing active changes is to use a safety-first classification system that detects dirty states and filters protected branches, requiring explicit user acknowledgment at two gates before any destructive removal.

Branch cleanup handles local branches with gone remotes by categorizing them for review rather than immediate deletion. It evaluates merge and PR evidence to determine if the branch is superseded or contains local work that needs to be kept.

Yes, you can delete related feature branches grouped by prefix safely. The workflow groups similarly named branches (e.g., feature/api-*) and evaluates their commit and PR history collectively to prevent scattering related iterations across deletion categories.

The Git branch deletion workflow requires two confirmation gates to prevent accidental data loss. It blocks destructive actions if the repository or worktrees are in a dirty state, ensuring you explicitly acknowledge and verify the categorized branches before removal.