repo-branches

Codex form of the /repo:branches command. Other commands appear as $repo-<verb> skills. Helper scripts and .claude/ paths below are relative to the repository root and exist when the Claude Code surface is installed alongside this one.

$repo-branches — Branch & Worktree Hygiene

Find stale local branches and worktrees that can be safely removed. Reports findings and waits for confirmation before deleting anything.

Usage

$repo-branches                   # Full audit
$repo-branches --prune           # Delete confirmed-safe branches after reporting

Steps

1. Inventory

Gather current state:

# Default branch
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|origin/||'

# Count local branches
git branch --list | wc -l

# List worktrees
git worktree list

# Identify active worktree branches (these are PROTECTED)
git worktree list --porcelain | grep '^branch ' | sed 's|branch refs/heads/||'

2. Categorize branches

For every local branch, classify it into one of these buckets:

PROTECTED (never delete)

• The default branch (main/master) and the currently checked-out branch
• Any branch currently checked out by a worktree
• Any branch with an open PR: gh api "repos/{owner}/{repo}/pulls?state=open&head={owner}:<branch>" --jq length
• Long-lived branches the repo's own docs (CLAUDE.md, CONTRIBUTING.md) name as release/project branches — if such a list exists, honor it

MERGED PR BRANCHES

• Branches matching common PR patterns: feature/*, fix/*, feat/*, pr-*
• Check whether a PR exists for the branch's head and is merged (the REST form below) — a count >= 1 means the branch is safe to delete
• Also safe: any branch fully merged into the default branch (git branch --merged <default>). Reachability is sufficient but not necessary — a squash-merged branch is never --merged, so its absence from that list means nothing. Step 5 decides.