skills.rest
Ouro-labs
Ouro-labsOFFICIAL
Explore all skills by this author →
GitHub

ce-clean-gone-branches

Identify and delete local branches with deleted remote tracking branches.

14|3|Updated May 7, 2026
Search Tags:#git#branch management#worktree management#repository cleanup#branch deletion
One-click install
npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-clean-gone-branches-ouro-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-clean-gone-branches
Source: https://github.com/Ouro-labs/ouroboros-plugins/tree/main/plugins/compound-engineering/assets/skills/ce-clean-gone-branches
Command: npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-clean-gone-branches-ouro-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps manage and clean up local branches that no longer exist on the remote, improving repository cleanliness and performance.

Core Features & Use Cases

  • Detect Gone Branches: Identifies branches with deleted remote tracking branches.
  • User Confirmation: Asks for confirmation before deleting branches.
  • Branch Deletion: Removes branches and associated worktrees if confirmed.
  • Use Case: When you want to remove old or abandoned branches from your local repository to keep it organized.

Quick Start

Run the 'clean-gone' script to clean up gone branches.

Frequently Asked Questions about ce-clean-gone-branches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delete local git branches that have been removed from the remote repository?▼

To delete local git branches removed from the remote, this Skill identifies branches with deleted remote tracking references and removes them after user confirmation. It ensures repository cleanliness by clearing out stale local branches and associated worktrees.

What is the best way to clean up stale local branches and worktrees in my git repository?▼

The best way to clean up stale local branches and worktrees is running the clean-gone script. It identifies local branches with deleted remote tracking branches and removes them after user confirmation to keep your repository organized.

Do I need to manually confirm before the script deletes gone branches?▼

Yes, user confirmation is required before deleting gone branches. The Skill identifies local branches with deleted remote tracking branches and asks for your confirmation before removing them and their associated worktrees.

Can I remove associated git worktrees when cleaning up branches with deleted remotes?▼

Yes, you can remove associated git worktrees when cleaning up branches. After detecting local branches with deleted remote tracking references and receiving user confirmation, the Skill removes both the branches and their associated worktrees.

Why does my local repository still show branches that no longer exist on the remote?▼

Your local repository shows branches that no longer exist on the remote because stale remote tracking references remain. This Skill identifies those gone branches and deletes them with user confirmation to prevent clutter and improve repository performance.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

git-cleanup

Analyze and clean up local git branches with dry-run previews.

Community
Intermediate
d3mingd3ming

git-clean-gone

Delete local Git branches with removed remote tracking branches and their worktrees.

Community
Intermediate
tom-xstom-xs

using-git-worktrees

Create and manage isolated git worktrees with submodule awareness.

Community
Advanced
MinhThang1009MinhThang1009
15

clean-gone

Remove local git branches marked [gone] and their associated worktrees.

Community
Intermediate