Skill

git-prune-branches-remote

Prunes remote Git branches merged into origin/main without touching local branches. Fetches latest info, excludes protected branches like main/develop, confirms before deletion.

Git

git-workflow

npx claudepluginhub takazudo/claude-resources

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Check and prune remote branches that have been merged:

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars7

Forks0

Last CommitMar 10, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Prune Branches (Remote)

Check and prune remote branches that have been merged:

Fetch the latest remote information using git fetch --prune

Get the list of all remote branches using git branch -r

For each remote branch, check if it has been merged into the remote main branch using git branch -r --merged origin/main (or appropriate main branch)

Exclude protected branches (main, master, develop, etc.)

Create a list of remote branches that are safe to delete

Present the deletion list to the user clearly

Ask for confirmation: "The following remote branches will be deleted. Proceed? (yes/no)"

If user confirms with "yes" or similar affirmative response, delete the remote branches using git push origin --delete <branch-name> for each branch

Report the results

Important: Never delete:

Protected branches: main, master, develop, development, staging, production

Branches that are not fully merged (unless explicitly requested)

Note: This operation affects the remote repository and cannot be easily undone. Ensure user confirmation before proceeding.