mcpbeat Sign in

Clean Branches Agent Skill

'Delete local branches whose PRs have been merged upstream. Checks GitHub PR prune branches, branch cleanup.'

786 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3472
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/brave/brave-core --skill clean-branches

The instruction itself

2 sections, as written by the author

Clean Branches - Delete Merged Local Branches

Clean up local branches by checking their GitHub PR status and deleting those

that have been merged.

Steps

  • Fetch and list branches — Fetch the latest remote state, then get all

local branches except master:

git fetch origin master
git branch --format='%(refname:short)' | grep -v '^master$'

Show the list to the user. If no branches exist besides master, report that

and stop.

  • Check merge status for each branch — Use multiple methods to detect

merges (including squash merges):

Method 1: Direct ancestry — Catches regular merges and fast-forwards:

git branch --merged origin/master --format='%(refname:short)'

Method 2: Squash merge detection via git cherry — For branches not caught

by method 1, check if all commits have equivalent patches in origin/master. A

- prefix means the patch already exists upstream:

git cherry -v origin/master <branch>

If ALL lines start with - (or output is empty), the branch has been

squash-merged.

Method 3: GitHub PR status (if gh is authenticated) — For remaining

branches:

# Check for merged PRs
gh pr list --head <branch> --state merged --json number,title,url

# Check for closed (not merged) PRs
gh pr list --head <branch> --state closed --json number,title,url,mergedAt

A PR is "closed without merge" when it appears in the closed list but has an

empty/null mergedAt field. If gh is not authenticated, skip this method.

Important: Always compare against origin/master (not local master) to

detect merges even when local master is stale.

  • Categorize branches into these groups:
  • Merged: Detected as merged by any method above → safe to delete
  • Closed (not merged): PR was closed without merging → flag for user

decision

  • No PR / Open PR: No PR found (and not detected as merged), or PR is

still open → skip

  • Display categorized list — Show the user a summary table with:
  • Branch name
  • Category (Merged / Closed / No PR / Open)
  • PR number and title (if available)
  • Detection method (ancestry / squash / PR status)
  • Confirm with user — Ask the user which branches to delete:
  • Pre-select "Merged" branches for deletion
  • Ask about "Closed (not merged)" branches individually
  • Never auto-delete "No PR" or "Open PR" branches
  • Delete confirmed branches — If currently on a branch being deleted,

switch to master first and fast-forward it:

git checkout master && git merge --ff-only origin/master
git branch -D <branch1> <branch2> ...

After deleting, prune stale remote tracking references:

git remote prune origin
  • Report results — Summarize:
  • How many branches were deleted
  • Which branches were kept and why

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take brave/clean-branches from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.