Git Branch Cleanup FAQs

Question 1

Is it safe to delete branches using this skill?

Accepted Answer

Yes. The skill uses the 'git branch -d' flag, which intentionally fails if a branch contains unmerged commits. Additionally, it requires your explicit confirmation for every branch identified for deletion.

Question 2

How does the skill define a 'stale' branch?

Accepted Answer

Stale branches are identified via a specialized script that analyzes commit history to find branches that have not seen active development for an extended period, even if they haven't been merged.

Question 3

Can I target specific branch types, like only 'fix/' branches?

Accepted Answer

Absolutely. You can provide an optional pattern as an argument (e.g., 'fix/*') to filter the cleanup analysis to only specific branch naming conventions.

Question 4

Can I use this to clean up remote branches on GitHub or GitLab?

Accepted Answer

Yes, the skill can perform remote deletions, but it will only do so if you explicitly request a remote cleanup during the confirmation process.

Question 5

Will it accidentally delete my main or production branches?

Accepted Answer

No. The skill includes a hardcoded safety rule that prevents the deletion of protected branches, including main, master, develop, and any branches matching the release/* pattern.

Git Branch Cleanup

主な機能

ユースケース

Git Branch Cleanup

主な機能

ユースケース