managing-worktrees

managing-worktrees is a skill for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 46 tokens per session (2,114 once invoked), scanned A, original, MIT.

A guide for using Git worktrees, which are extra working folders linked to one repository so you can check out different branches at the same time.

In plain words
What is it for?
Creating, listing, checking, and cleaning up worktrees for parallel branch development.
Why use it?
It avoids repeatedly stashing changes or switching branches, and keeps parallel work, reviews, and urgent fixes isolated.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/project.

Part of the github-workflows plugin — 8 skills, 9 commands, 4 agents shipped together

Good fit Creating, listing, checking, and cleaning up worktrees for parallel branch development.

Compare 6 skills 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 C0ntr0lledCha0s/claude-code-plugin-automations
Claude Code
/plugin install github-workflows

Made for: Claude Code.

Or install github-workflows, the plugin that ships this one along with the rest of its 8 skills, 9 commands, 4 agents.

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 managing-worktrees

README.md
[![agentmods](https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees/github.svg)](https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees)
Your own site
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees/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 managing-worktrees

Your own site · 80×15
<a href="https://agentmods.dev/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees"><img src="https://agentmods.dev/badge/skills/c0ntr0lledcha0s/claude-code-plugin-automations/managing-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,114 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.00046 $0.02114
Opus 5 $0.00023 $0.01057
Sonnet 5 $0.00009 $0.00423
Haiku 4.5 $0.00005 $0.00211

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

Security

Grade A, and why

managing-worktrees 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 8d 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.

github-workflows/skills/managing-worktrees/SKILL.md · 360 lines

How it starts

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

Managing Worktrees Skill

You are a git worktree management expert specializing in parallel development workflows. You understand how worktrees enable developers to work on multiple branches simultaneously without stashing or context switching.

When to Use This Skill

Auto-invoke this skill when the conversation involves:

  • Creating git worktrees for parallel development
  • Listing or checking worktree status
  • Cleaning up merged worktrees
  • Working on multiple branches simultaneously
  • Isolated development environments
  • Emergency hotfix workflows that need isolation
  • PR review without disrupting current work
  • Keywords: "worktree", "parallel development", "multiple branches", "work on two branches"

Do NOT auto-invoke for:

  • Simple branch operations (use managing-branches)
  • General git operations not involving worktrees

Your Expertise

1. Worktree Fundamentals

Understanding git worktrees:

  • What is a worktree?: A linked working directory attached to a repository
  • Shared history: All worktrees share the same git history and objects
  • Branch isolation: Each branch can only be checked out in ONE worktree
  • Independent state: Each worktree has its own staging area and working directory

Key concepts:

  • Main worktree: The original clone location
  • Linked worktrees: Additional working directories
  • Worktree path: Where the worktree files are stored
  • Each worktree is a full working copy

2. Creating Worktrees

For existing branches:

# Basic creation (auto-generate path)
git worktree add ../worktrees/auth feature/auth

# Custom path
git worktree add /custom/path feature/auth

For new branches:

# Create branch and worktree together
git worktree add -b feature/new-feature ../worktrees/new-feature main

Path conventions:

  • Default base: ../worktrees/
  • Structure: ../worktrees/<branch-slug>
  • Avoid nested paths within repository

3. Listing Worktrees

# List all worktrees
git worktree list

# Detailed format
git worktree list --porcelain

# Sample output:
# /home/user/project        abc1234 [main]
# /home/user/worktrees/auth def5678 [feature/auth]

Read the full file on GitHub · 360 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. 8d ago First seen · 360 lines · 46 tokens per session scan A f34bc1e13852

Subscribe to this mod's changes

managing-worktrees is a skill published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 2,114 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-31.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens