clean-branches

To delete local git branches after merging a PR, you need to fetch remote updates and prune branches marked as deleted. This skill automates that branch cleanup process to remove stale local refs and keep your repository organized.

The best way to automate branch cleanup is to run a process that lists and removes local branches marked as deleted on the remote. This skill handles the fetch and prune commands required to clear those obsolete branches automatically.

To remove git worktrees associated with deleted remote branches, you must prune the worktree references alongside the local branch deletion. This skill automates worktree removal to ensure linked workspace directories are cleaned up post-merge.

No specific git tools or plugins are required. This skill relies on standard git commands to fetch, prune, list, and remove branches and worktrees, functioning within your existing repository maintenance environment without extra dependencies.

You should run post-merge branch cleanup immediately after a pull request is merged and the remote branch is deleted. Running the skill at this point prevents local clutter by ensuring obsolete branches and worktrees are removed.

Stale local branches remain because local git repositories do not automatically sync remote deletions. You must execute a fetch and prune operation to detect and remove local branches marked as deleted on the remote.