git-cleanup-merged

To clean up merged branches safely, this Skill detects branches merged into a target branch and requires explicit user confirmation before deletion. It enforces safety rules by never deleting the target or main branch, reporting a clear summary of removed and skipped branches.

Yes, you can remove active worktrees after merging. The workflow identifies worktrees associated with branches merged into a target branch, summarizes the candidates for cleanup, and asks for your confirmation before removing them.

The safest way to prune stale branches is to use a workflow that detects merges against a target branch and requires user confirmation. This Skill defaults to using the safe -d flag for deletion and only applies the forceful -D flag with explicit user consent.

Yes, git branch cleanup works against a target branch other than main. The default target is main, but you can specify a different target branch, and the workflow will detect all local branches and worktrees merged into that specified target.

A confirmation prompt prevents the accidental loss of unmerged work. Before deleting merged branches and worktrees, this Skill provides a clear summary of what will be removed and skipped, ensuring you review the candidates and explicitly approve the action before any deletion occurs.