New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Clean Branches

by dyoshikawa in dyoshikawa/rulesync

Clean up unnecessary local branches and prune stale remote-tracking branches

MITAuto-check passedDevelopment

Install Clean Branches

skills CLI
$ npx skills add dyoshikawa/rulesync --skill clean-branches -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync clean-branches --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/clean-branches .claude/skills/clean-branches && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clean-branches
GitHub stars
1.5k
Used in
1 other repo
Token cost
~481 tokens
SKILL.md length
232 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Clean up unnecessary local branches and prune stale remote-tracking branches

  • Works in 5 steps: Inspect Current State → Refresh Remote State → Select Branches to Delete → …
  • Development work in your project
  • SKILL.md covers Step 1: Inspect Current State, Step 2: Refresh Remote State, Step 3: Select Branches to… and Step 4: Delete Branches, plus 1 more section
  • Calls git

What it does

Clean Branches is an agent skill from dyoshikawa/rulesync. Clean up unnecessary local branches and prune stale remote-tracking branches

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/clean-branches”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Inspect Current State
  2. Refresh Remote State
  3. Select Branches to Delete
  4. Delete Branches
  5. Report Result

What it can do on your machine

Read from SKILL.md and the folder at commit 2c577d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clean Branches loads about 481 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 232 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~481

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 2c577d0, republished under its MIT licence (© dyoshikawa). 232 words, ~481 tokens.

Download SKILL.mdSave it as .claude/skills/clean-branches/SKILL.md (or your agent's skills folder).
name
clean-branches
description
Clean up unnecessary local branches and prune stale remote-tracking branches
targets
*

Clean Branches

Clean up unnecessary local branches and prune stale remote-tracking branches.

Step 1: Inspect Current State

Run the following:

  • git branch --show-current
  • git branch --format='%(refname:short)'
  • git remote show origin
  • git branch -vv

Identify:

  • The current branch
  • The default branch (for example main or master)
  • Branches whose upstream has been deleted

After identifying the default branch, list branches already merged into it:

  • git branch --merged <default-branch>

If you want to use the remote-tracking branch as the source of truth, use:

  • git branch --merged origin/<default-branch>

Step 2: Refresh Remote State

Update remote refs and prune deleted remote branches:

bash
git fetch --prune

If needed, also run:

bash
git remote prune origin

Step 3: Select Branches to Delete

Delete only branches that are clearly unnecessary.

Safe candidates include:

  • Local branches already merged into the default branch you identified above
  • Local branches whose upstream branch is gone and are no longer needed

Never delete:

  • The current branch
  • The default branch
  • Branches that are not fully merged unless the user explicitly asks for force deletion

If there is any ambiguity, show the candidate branches to the user and ask for confirmation.

Step 4: Delete Branches

For merged branches, delete them safely:

bash
git branch -d <branch-name>

Only if the user explicitly approves force deletion for unmerged branches, use:

bash
git branch -D <branch-name>

Delete branches one by one, not with a broad wildcard command.

Step 5: Report Result

Summarize:

  • Which branches were deleted
  • Which branches were skipped and why
  • Whether stale remote-tracking branches were pruned

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/clean-branches of dyoshikawa/rulesync.

Open the folder on GitHubat commit 2c577d0

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in dyoshikawa/rulesync, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Clean Branches next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clean Branches compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clean Branches this skilldyoshikawa/rulesync1.5k1 repos~481Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo

  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Commit Push PR

    dyoshikawa/rulesync

    Commit current changes, push to remote, and create or update a pull request.

    1.5k GitHub stars~458 tokensUpdated today
    Auto-check passed

  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Clean Branches

What does Clean Branches do?

Clean up unnecessary local branches and prune stale remote-tracking branches. Clean Branches is an agent skill from dyoshikawa/rulesync.

When should I use Clean Branches?

Clean Branches fits situations like: development work in your project.

How do I install Clean Branches in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill clean-branches -a claude-code`. Or copy the skill folder (.rulesync/skills/clean-branches in dyoshikawa/rulesync) into .claude/skills/clean-branches in your project. Claude Code loads it when a task matches its description.

How do I install Clean Branches in Codex?

Run `npx skills add dyoshikawa/rulesync --skill clean-branches -a codex`. Or copy the skill folder (.rulesync/skills/clean-branches in dyoshikawa/rulesync) into .agents/skills/clean-branches in your project. Codex loads it when a task matches its description.

Can I use Clean Branches in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill clean-branches -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-branches, .gemini/skills/clean-branches, .github/skills/clean-branches and .opencode/skills/clean-branches in your project.

What does Clean Branches need to run?

Going by SKILL.md and its folder, Clean Branches needs the command-line tools its instructions call (git).

Does Clean Branches access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Clean Branches safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clean Branches use?

Clean Branches is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clean Branches use?

About 481 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clean Branches?

Skills that share tags, products or a category with Clean Branches: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clean Branches?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,508 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.