Git Cleanup FAQs

Question 1

Is it safe to use this skill on my primary repositories?

Accepted Answer

Yes, the skill is designed with a 'Safety First' principle. It never invokes automatically and requires two separate user confirmations—one after the initial analysis and another before the final execution.

Question 2

Can I choose which specific branches to delete?

Accepted Answer

Absolutely. After the analysis phase, you can choose to delete all recommended branches, specific categories (like merged only), or select individual branches one by one.

Question 3

Will I lose uncommitted work in my worktrees?

Accepted Answer

No, the skill performs a dirty state check on all worktrees. If uncommitted changes are detected, it will prominently warn you or refuse to remove the worktree to prevent data loss.

Question 4

How does it handle branches that were squash-merged?

Accepted Answer

Since standard git commands often fail to recognize squash-merged branches as 'merged,' this skill investigates PR history and commit keywords to identify them and uses force-delete only when safety is confirmed.

Question 5

Does this skill delete branches on GitHub or other remotes?

Accepted Answer

No, this skill is strictly for local cleanup. It analyzes the state of your remote branches to make recommendations, but it only performs deletions on your local machine.

Git Cleanup

Key Features

Use Cases

Git Cleanup

Key Features

Use Cases