remove-worktree

remove-worktree is a command for Claude Code from gopherguides/gopher-ai. It costs 9 tokens per session (1,604 once invoked), scanned A, original, MIT.

An interactive command for selecting and removing one git worktree, which is a separate working folder connected to the same repository.

In plain words
What is it for?
Use it when you need to choose one worktree to delete and handle its cleanup interactively.
Why use it?
It helps remove a specific worktree when automatic cleanup is not appropriate, including cases where its issue is still open or its branch is not merged.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the go-workflow plugin — 11 skills, 3 commands, 4 agents, 4 hooks shipped together

Good fit Use it when you need to choose one worktree to delete and handle its cleanup interactively.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add gopherguides/gopher-ai
Claude Code
/plugin install go-workflow

Made for: Claude Code.

Or install go-workflow, the plugin that ships this one along with the rest of its 11 skills, 3 commands, 4 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for remove-worktree

README.md
[![agentmods](https://agentmods.dev/badge/commands/gopherguides/gopher-ai/remove-worktree/github.svg)](https://agentmods.dev/commands/gopherguides/gopher-ai/remove-worktree)
Your own site
<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/remove-worktree"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/remove-worktree/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for remove-worktree

Your own site · 80×15
<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/remove-worktree"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/remove-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,604 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00009 $0.01604
Opus 5.5 $0.00004 $0.00642
Sonnet 5.5 $0.00002 $0.00321
Haiku 4.5 $0.00001 $0.00160

Measured 1mo ago against content hash ebdb84497f1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

remove-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 1mo 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/remove-worktree.md · 171 lines

How it starts

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

Remove Worktree

This command interactively removes a single git worktree. Unlike /prune-worktree which auto-removes all safe worktrees, this command lets you select a specific worktree and handles cases where the issue isn't closed or branch isn't merged.

Usage: /remove-worktree (no arguments - interactive selection)

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"

Steps

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

1. Get Repository Info

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

2. List All Issue Worktrees

!echo "Scanning for issue worktrees..." !git worktree list

Filter for worktrees matching the {REPO_NAME}-issue-* pattern and display them as a numbered list.

!git worktree list | grep -E "/${REPO_NAME}-issue-[0-9]+" | cat -n

If no issue worktrees are found, inform the user and stop: "No issue worktrees found matching the pattern '{REPO_NAME}-issue-*'"

3. Ask User to Select Worktree

Use AskUserQuestion to ask: "Which worktree would you like to remove? Enter the number from the list above, or the full path."

Store the selected worktree path and extract:

  • WORKTREE_PATH: The full path to the worktree
  • BRANCH_NAME: The branch associated with the worktree
  • ISSUE_NUM: The issue number extracted from the directory name

Read the full file on GitHub · 171 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. 1mo ago First seen · 171 lines · 9 tokens per session scan A ebdb84497f1c

Subscribe to this mod's changes

remove-worktree is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 1,604 once invoked, about $0.0000 per session on Opus 5.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.