stevefeldman/clean-branch
skills/clean-branch/SKILL.md
Safely clean up merged, stale, and unnecessary git branches with dry-run preview
$ install --global
skillsauthnpx skillsauth add stevefeldman/agents-skills clean-branchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 8:04 AM132.2s1 file scanned
SKILL.md
- name:
- clean-branch
- description:
- Safely clean up merged, stale, and unnecessary git branches with dry-run preview
Clean Branches
Safely clean up merged, stale, and unnecessary git branches across any repository.
Usage
/clean-branch # Dry-run analysis of all branches
/clean-branch --execute # Actually delete after confirmation
/clean-branch --stale-days 60 # Consider branches older than 60 days stale
Instructions
Follow this approach to clean up git branches: $ARGUMENTS
Default behavior is dry-run — show what would be deleted without deleting anything. Only execute deletions when the user explicitly confirms.
1. Repository State Analysis
git status
git branch -a
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'
- Check current branch and ensure working directory is clean
- Identify the main/default branch name
- List all local and remote branches
2. Categorize Branches
Identify and group branches into categories:
Merged branches (safe to delete):
git branch --merged main | grep -v "main\|master\|develop\|\*"
Stale branches (no activity in 30+ days):
git for-each-ref --format='%(refname:short) %(committerdate:relative)' refs/heads/
Protected branches (never delete):
main,master,develop,staging,production
Active branches (unmerged, recent activity):
- List for reference but do not suggest deletion
3. Present Dry-Run Report
## Branch Cleanup Report
### Safe to Delete (merged into main)
- feature/user-auth (merged 3 days ago)
- fix/login-bug (merged 1 week ago)
### Stale (no activity in 30+ days)
- feature/old-experiment (last commit: 45 days ago, NOT merged)
⚠️ Has 3 unmerged commits — review before deleting
### Protected (will not touch)
- main, develop
### Active (keeping)
- feature/new-dashboard (last commit: 2 days ago)
4. Execute Cleanup (only when confirmed)
If the user confirms, proceed:
- Switch to main branch and pull latest
- Delete merged local branches with
git branch -d - Prune remote tracking branches with
git remote prune origin - For stale unmerged branches, ask individually before using
git branch -D
5. Verify Results
git branch -a
Report what was deleted and confirm protected branches are intact.
Recovery note: Deleted branches can be recovered via git reflog within the reflog expiry period (default 90 days).
Related Skills
stevefeldman/dependency-security-audit
development
VerifiedTrustedCommunity
Use when reviewing Dependabot alerts, npm audit findings, govulncheck output, or CVE reports on a JavaScript/Node.js or Go project — especially when triaging multiple alerts across direct and transitive dependencies to assess real-world risk and produce a remediation plan.
3SKILL.mdUpdated May 28, 2026
stevefeldman/pr-evidence
development
VerifiedTrustedCommunity
Use when a code review finding needs proof — write a focused test in JavaScript or Go that either confirms the issue is real or exposes it as over-engineering hyperbole. Trigger after code-review or code-review-skill findings are presented and evidence is requested.
3SKILL.mdUpdated May 22, 2026
stevefeldman/software-estimation
development
VerifiedTrustedCommunity
Produce data-driven software delivery estimates by analyzing historical JIRA tickets, git activity, and engineer track records, then matching the new work against the most similar past tickets. Use this skill whenever the user asks "how long will this take", wants to estimate a piece of work, scope an epic, plan a sprint, or estimate delivery for JIRA stories or a Figma design. Also use whenever the user wants developer-to-work assignment recommendations based on history, wants to optimize an estimate by adding or reallocating engineers, or asks "what's the fastest way to ship this" or "who should work on this". Especially trigger when the user provides JIRA ticket IDs, JIRA story links, or Figma designs together with any indication of a team that will execute the work.
3SKILL.mdUpdated May 16, 2026
stevefeldman/automation-rubric
tools
VerifiedTrustedCommunity
Use when auditing an existing test suite for quality and coverage gaps, evaluating Playwright migration readiness, scoring automation against a world-class e-commerce standard, or guiding the creation of new tests. Applicable to Selenium, WebdriverIO, and Playwright suites.
3SKILL.mdUpdated May 12, 2026