clean-branches

To delete git branches merged into main, you need a cleanup process that identifies merged work and removes those branches locally and remotely. This skill detects regular and squash merges, safely deleting stale branches while protecting upstream and main.

Yes, you can detect and remove squash-merged branches by checking if the branch's commits are already in main. This skill identifies squash-merged branches locally and on forks, pruning tracking refs and deleting them safely without touching upstream or main.

To clean up fork remote branches without affecting upstream, you must target only fork-specific remotes and skip upstream or main branches. This skill handles fork-only deletion, prunes tracking refs, and enforces safeguards against touching upstream or main branches.

The best way to prune stale git branches after a merge is to use an automated cleanup workflow that detects merged work and prompts for approval. This skill identifies merged branches locally and on forks, offering optional user approval before deletion.

Yes, git branch cleanup works for both individual developers and teams managing repositories. This skill is applicable to any repository context, identifying and removing merged branches locally and on forks while safeguarding upstream and main.