prune-worktree

A command that removes Git worktrees—separate working folders for branches—when their GitHub issues are closed and their pull requests are merged.

In plain words
What is it for?
Use it to scan issue worktrees, confirm their GitHub and Git status, remove completed ones, and clean up related local branches.
Why use it?
It clears completed issue worktrees and local branches without requiring you to check each one manually. Safety checks help avoid removing work with uncommitted changes or unmerged branches.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/gopherguides/gopher-ai/prune-worktree
Clone the repo
git clone --depth 1 https://github.com/gopherguides/gopher-ai
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00889
Opus 5 $0.00004 $0.00445
Sonnet 5 $0.00002 $0.00178
Haiku 4.5 $0.00001 $0.00089

Measured 2d ago against content hash d243b9140a03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prune-worktree scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/go-workflow/commands/prune-worktree.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prune Issue Worktrees

This command safely removes worktrees for completed GitHub issues.

What it does:

  1. Scans for worktrees matching the {reponame}-issue-* pattern
  2. Checks each associated GitHub issue status
  3. Verifies branches are merged into the default branch
  4. Removes worktrees for closed/merged issues
  5. Cleans up local branches

Safety checks:

  • Only removes closed issues with merged PRs
  • Warns about uncommitted changes
  • Provides manual commands for edge cases

Usage: /prune-worktree (no arguments needed)

Clear Worktree State

Clear any active worktree state so the pre-tool-use hook doesn't block cleanup commands: !"${CLAUDE_PLUGIN_ROOT}/scripts/worktree-state.sh" clear 2>/dev/null || true

Context

  • Repository name: !basename \git rev-parse --show-toplevel 2>/dev/null` 2>/dev/null || echo "unknown"`
  • Default branch: !git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //' || echo "main"
  • All worktrees: !git worktree list 2>&1 || echo "No worktrees found"
  • Issue worktrees: !git worktree list 2>/dev/null | grep -E "issue-[0-9]+" || echo "No issue worktrees found"

Scan and Cleanup

CRITICAL: When executing bash commands below, use backticks (`) for command substitution, NOT $(). Claude Code has a bug that mangles $() syntax into broken commands.

CRITICAL: Before removing any worktree, first cd to the main repository directory. This prevents CWD invalidation errors if running from a worktree that will be removed:

!cd git worktree list | head -1 | awk '{print $1}'

First, get the repository name:

!REPO_NAME=basename \git rev-parse --show-toplevel`` !echo "Repository: $REPO_NAME"

List all worktrees:

!git worktree list

For each worktree matching the {REPO_NAME}-issue-* pattern:

  1. Extract issue number from directory name using: grep -oE '[0-9]+'
  2. Validate issue number is numeric (security: prevent command injection)
  3. Check GitHub issue status: gh issue view "$ISSUE_NUM" --json state
  4. Check if branch is merged: git branch --merged "$DEFAULT_BRANCH" | grep -F "$BRANCH_NAME"
  5. If issue is closed AND branch is merged, offer to remove

Read the full file on GitHub · 102 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 102 lines · 8 tokens per session scan A d243b9140a03

Subscribe to this mod's changes

prune-worktree is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 889 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.