Dev10x:git-branch-prune

Classify and prune git branches with merge verification and user approval.

7|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-git-branch-prune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:git-branch-prune
Source: https://github.com/Dev10x-Guru/Dev10x-Claude/tree/main/skills/git-branch-prune
Command: npx skills add https://github.com/Dev10x-Guru/Dev10x-Claude --skill dev10x-git-branch-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the classification and pruning of stale local branches in a git repository, ensuring that branches are pruned only after user approval.

Core Features & Use Cases

  • Branch Classification: Classifies branches into categories (A, B, C, D) based on their merge history and content.
  • User Approval: Requests user approval before deleting branches.
  • Use Case: For use in rebase-merge repositories where traditional pruning methods may miss many stale branches, this Skill ensures that branches are pruned accurately and safely.

Quick Start

Run the 'Dev10x:git-branch-prune' command to classify and prune stale branches in your local git repository.

Frequently Asked Questions about Dev10x:git-branch-prune

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

FAQPage Schema
How do I prune stale local git branches in a rebase-merge repository?

Git branch pruning is the process of deleting stale local branches after verifying their merge history. This Skill automates classification into categories and requires your explicit approval before deleting branches to ensure safe removal.

Why does traditional git branch pruning miss stale branches in rebase-merge repositories?

Traditional git branch pruning misses stale branches in rebase-merge repositories because standard methods fail to verify rebased commits accurately. This Skill solves the problem by classifying branches based on their specific merge history and content.

How do I automate git branch deletion safely with user approval?

You automate git branch deletion safely by running the prune command, which classifies branches into categories and prompts for user approval. This ensures you explicitly confirm every branch deletion before any removal occurs.

Does this git branch pruning tool require manual confirmation before deleting branches?

Yes, this git branch pruning tool requires manual user confirmation before deleting branches. It automates the classification of stale branches but always requests your explicit approval to ensure safe repo maintenance.

What is the best way to classify stale git branches before pruning?

The best way to classify stale git branches before pruning is to use an automated tool that categorizes them by merge history and content. This Skill classifies branches into categories and verifies merges for accurate pruning.