ce-clean-gone-branches

To clean up stale local branches, this Skill performs a git fetch and prune operation to detect branches no longer tracked on the remote. It then asks for user confirmation before deleting those local branches to prevent accidental data loss.

The best way to keep your repository tidy is to eradicate unused branches through an automated fetch and prune workflow. This Skill detects branches lacking a corresponding remote branch, removes associated worktrees, and deletes them after user confirmation.

Yes, branch cleanup does remove git worktrees associated with deleted branches. When the Skill identifies and removes locally tracked branches that are no longer present on the remote, it handles the removal of linked worktrees as well to maintain a clean repository state.

No, you do not need external dependencies to remove locally tracked branches gone from the remote. The Skill assumes a Git environment, uses built-in fetch and prune commands, and requires no additional software to perform its branch cleanup operations.

Stale branch removal asks for confirmation before deleting local branches to prevent accidental loss of data. This user confirmation step ensures that you have explicit control over which branches are eradicated during the repository synchronization process.