branch-cleanup

To safely delete stale git branches, you can fetch with prune, classify branches as merged or unmerged relative to main, and review a report before approving safe local deletion (-d) and remote deletion via git push --delete. This prevents accidental loss of active work.

Finding merged remote branches for repository cleanup involves fetching remote refs with prune and auditing them against your main branch. The Skill classifies branches by merged status and last commit recency, flagging potentially stale targets while preserving active development branches.

Cleaning up local git branches without losing unmerged work requires classifying branches relative to main to identify fully merged targets. The Skill avoids force deletion (-D) and protects the currently checked-out branch, requiring explicit approval before removing any redundant branch history.

Yes, git branch cleanup requires explicit approval before deleting remote branches. The Skill presents a categorized report-first presentation showing last commit and ahead counts, and only executes remote deletion via git push --delete after you explicitly approve the proposed removals.

You can prevent accidental deletion of main or active branches during repository hygiene maintenance by using a safety-first classification approach. The Skill blocks destructive actions on main and the checked-out branch, avoiding force deletion and categorizing targets as active or potentially stale based on commit recency.

You should avoid force deleting git branches with git branch -D when performing repository hygiene, as it bypasses merged status checks. Instead, use safe local deletion (-d) after verifying branch classification relative to main, ensuring unmerged work is preserved and only redundant history is removed.