git-prune-worktrees

To safely clean up stale Git worktrees and merged branches, run a dry-run preview to review planned removals, then execute the script with the --yes flag to apply the deletion plan while respecting protected refs.

Yes, you can preview Git worktree and branch deletions by running a dry-run, which generates a JSON-like report of planned actions, skips, and errors without modifying your repository.

You can exclude specific branches from a Git worktree cleanup by using user-specified include/exclude patterns, which selectively target branches for removal while enforcing protection for critical refs.

The best way to automate removing multiple stale Git worktrees is using a plan-driven workflow that optionally fetches remote updates, applies include/exclude patterns, and requires a --yes approval to execute the pruning.

Yes, Git worktree pruning respects protected branches by evaluating removal plans against protected refs, ensuring critical branches are skipped during the automated cleanup of merged local branches and stale worktrees.

A plan-driven workflow for Git branch management reduces maintenance clutter by safely validating removal actions, providing JSON-like reporting of errors and skips, and preventing accidental deletion of unmerged or protected branches.