A git worktree manager for creating separate working folders from one repository. A worktree lets you work on an issue or pull request without changing your main checkout.

Use it to create a worktree for an issue or pull request, remove one selected worktree, or clean up completed worktrees.

It keeps parallel tasks isolated and makes it easier to remove finished task folders. It also prevents unclear requests from changing worktrees accidentally.

worktree — Skill by gopherguides

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 skills/gopherguides/gopher-ai/worktree

Any agent

npx skills add gopherguides/gopher-ai --skill worktree

Clone the repo

git clone --depth 1 https://github.com/gopherguides/gopher-ai

Made for: Claude Code, Codex.

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

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 592 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.

Model	Per session	Once invoked
Fable 5	$0.00043	$0.00592
Opus 5	$0.00022	$0.00296
Sonnet 5	$0.00009	$0.00118
Haiku 4.5	$0.00004	$0.00059

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

Security

Grade A, and why

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 3d 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/skills/worktree/SKILL.md · 51 lines

How it starts

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

Worktree

Manage git worktrees for isolated per-issue/per-PR work. Three sub-actions, each in its own sibling file.

Before requesting decisions, read ${CLAUDE_PLUGIN_ROOT}/lib/driver-interaction.md and follow its cross-platform capability-binding rules.

Read ${CLAUDE_PLUGIN_ROOT}/lib/decision-gates.md before resolving action, target, consent, or cleanup choices.

Action selection

User intent	Sibling	Slash command
Create one worktree for an issue or PR	`create.md`	`/create-worktree <num>`
Remove a specific worktree (interactively)	`remove.md`	`/remove-worktree`
Batch-clean all completed worktrees	`prune.md`	`/prune-worktree`

Match the user's request to one of the three rows, then read the corresponding sibling for the full procedure.

If the request does not identify one action, follow the shared missing-intent gate. Request create, remove, or prune intent and stop before mutating worktrees.

Conventions (apply to all three actions)

Worktree path: ../<reponame>-issue-<num>-<title-slug>/ — sibling to the source repo, never inside it
Branch name: issue-<num>-<title-slug>
Title slug: lowercase, alnum + hyphens, derived from gh issue view --json title
Identifier rule: issue-<NUM>- prefix is the trusted issue marker on a branch — fix/2fa-login contains a number but is NOT an issue branch
Default branch: git remote show origin | grep 'HEAD branch' (handles repos with main vs master vs custom)
State file: ${CLAUDE_PLUGIN_ROOT}/scripts/worktree-state.sh registers the active worktree so the pre-tool-use hook blocks accidental edits to the source repo

Prerequisites (all three)

gh CLI installed and authenticated
Run from inside a git repository (any worktree of the repo, not just the main checkout)

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

3d ago First seen · 51 lines · 43 tokens per session scan A ea13f5e2b23b

Subscribe to this mod's changes

worktree is a skill published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 592 once invoked, about $0.0002 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.

Git and workflow

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

worktree