drn/prune
agents/skills/prune/SKILL.md
Clean up merged and stale git branches, prune old local and remote branches safely. Use for cleaning up old branches or pruning stale remotes.
$ install --global
skillsauthnpx skillsauth add drn/dots pruneInstall 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 21, 2026, 10:55 AM51.0s2 files scanned
SKILL.md
- name:
- prune
- allowed-tools:
- Bash(bash ~/.claude/skills/prune/scripts/prune.sh:*), Bash(bash agents/skills/prune/scripts/prune.sh:*)
- description:
- Clean up merged and stale git branches, prune old local and remote branches safely. Use for cleaning up old branches or pruning stale remotes.
- disable-model-invocation:
- true
Branch Cleanup
Delete merged and stale local branches safely, with preview and confirmation.
Arguments
$ARGUMENTS- Optional:--stale-days <N>to override the 30-day stale threshold,--remoteto also delete remote branches
Context
- Current branch: !
git branch --show-current - Remote: !
git remote 2>/dev/null | head -5
Instructions
Resolve the script path — use the first that exists:
~/.claude/skills/prune/scripts/prune.sh(deployed via symlink)agents/skills/prune/scripts/prune.sh(repo-relative, for development/workspaces)
Step 1: Preview branches
Run the preview command, forwarding any --stale-days argument:
bash <script-path> preview [--stale-days N]
Handle the exit code:
- Exit 0 — Present the output as a formatted table (see format below). Proceed to Step 2.
- Exit 3 — Tell the user: "All branches are current — nothing to prune." and stop.
- Exit 1 — Report the error from stderr.
Format the preview output as:
## Branch Cleanup Preview
### Merged (safe to delete)
| Branch | Last Commit | Merged Into |
|--------|------------|-------------|
| <branch> | <date> | <default> |
### Stale (no commits in N days)
| Branch | Last Commit |
|--------|------------|
| <branch> | <date> |
### Skipped
| Branch | Reason |
|--------|--------|
| <branch> | <reason> |
Step 2: Confirm and delete
Ask the user which branches to delete. Accept "all", specific branch names, or "none".
For confirmed branches, run the delete command:
bash <script-path> delete [--remote] <branch1> [branch2 ...]
Include --remote only if the user passed it in $ARGUMENTS.
Handle the exit code:
- Exit 0 — Show the output block verbatim as your final response.
- Exit 1 — Report the error from stderr.
Related Skills
drn/address-comments
development
VerifiedTrustedCommunity
Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
23SKILL.mdUpdated May 16, 2026
drn/rereview-loop
tools
VerifiedTrustedCommunity
Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-visual-explainer
development
VerifiedTrustedCommunity
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-setup-goal
development
VerifiedTrustedCommunity
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
23SKILL.mdUpdated May 13, 2026