prune

Categorize stale git branches by merge status and open pull requests.

1|1|Updated Feb 9, 2026

Search Tags:#git #developer tools #version control #cleanup #repository #branch management

Ready to run

npx skills add https://github.com/MattKotsenas/agent-plugins --skill prune-mattkotsenas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prune
Source: https://github.com/MattKotsenas/agent-plugins/tree/main/plugins/prune/skills/prune
Command: npx skills add https://github.com/MattKotsenas/agent-plugins --skill prune-mattkotsenas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you manage your Git repository by identifying and cleaning up old, merged, or otherwise unnecessary branches, keeping your project tidy and focused.

Core Features & Use Cases

Branch Categorization: Automatically categorizes branches as merged, renamed, having open PRs, or unknown.
Interactive Review: Presents branches in a clear, card-like format, grouped by suggested action (delete, keep).
Use Case: After completing a feature, you want to clean up all the branches that have already been merged into main or dev to avoid clutter.

Quick Start

Use the prune skill to clean up stale git branches in your repository.

Frequently Asked Questions about prune

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

FAQPage Schema

How do I clean up stale git branches in my local repository?▼

To clean up stale git branches, you can use an automated tool that scans local and remote branches, categorizes them by merge status, and presents them for interactive deletion. This prevents you from accidentally removing active work.

Can I detect and remove merged git branches without deleting ones with open pull requests?▼

Yes, detecting branches with open pull requests is supported during the cleanup process. The tool checks upstream status and PR activity, categorizing branches with open PRs as 'keep' to prevent accidental deletion while removing merged ones.

What is the best way to manage local branch cleanup when using squash-merge workflows?▼

Managing local branch cleanup with squash-merge workflows requires detecting branches that have been squashed and merged upstream. This tool supports squash-merge workflows by scanning upstream status and categorizing those branches for safe deletion.

Does the git branch deletion process support rollback if I remove the wrong branch?▼

Yes, rollback options are supported during the git branch deletion process. If you accidentally remove a necessary branch, the rollback functionality allows you to restore it, ensuring safe repository management during interactive cleanup.

How does automated branch categorization work for git repository cleanup?▼

Automated branch categorization for git repository cleanup works by scanning local and remote branches against upstream status and open pull requests. It groups branches into categories like merged, renamed, or unknown, suggesting keep or delete actions.