Menu
Safely clean up merged, stale, and unnecessary git branches with dry-run preview
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
PR-focused code review with structured checklist, severity ratings, and actionable feedback
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.
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.
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.
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.
AI-powered observability with Grafana MCP — translates natural language to metrics, logs, and trace queries to diagnose issues like a senior SRE
| name | clean-branch |
| description | Safely clean up merged, stale, and unnecessary git branches with dry-run preview |
Safely clean up merged, stale, and unnecessary git branches across any repository.
/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
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.
git status
git branch -a
git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'
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, productionActive branches (unmerged, recent activity):
## 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)
If the user confirms, proceed:
git branch -dgit remote prune origingit branch -Dgit 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).