Git Worktree Management

Git Worktree Management is a skill for Claude Code from ChrisMckerracher/claude-dream-team. It costs 38 tokens per session (1,299 once invoked), scanned A, original, MIT.

A set of instructions for using Git worktrees, which let separate branches of one project live in separate folders at the same time.

In plain words
What is it for?
Use it to create isolated task folders, name branches, keep them updated, submit changes for review, run tests, merge work, and clean up finished worktrees.
Why use it?
It prevents parallel coding tasks from changing the same files or branch unexpectedly. It also defines a shared process for creating, reviewing, merging, and removing those workspaces.

Skill for Claude Code

Written for Claude Code: PreToolUse hook event.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is WORKTREE_DIR="../worktrees/${AGENT_NAME}-task-${TASK_ID}".

Part of the dream-team plugin — 11 skills, 3 hooks shipped together

Good fit Use it to create isolated task folders, name branches, keep them updated, submit changes for review, run tests, merge work, and clean up finished worktrees.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/ChrisMckerracher/claude-dream-team
agentmods
npx agentmods add skills/chrismckerracher/claude-dream-team/git-worktree

Made for: Claude Code.

Or install dream-team, the plugin that ships this one along with the rest of its 11 skills, 3 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 Git Worktree Management

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrismckerracher/claude-dream-team/git-worktree/github.svg)](https://agentmods.dev/skills/chrismckerracher/claude-dream-team/git-worktree)
Your own site
<a href="https://agentmods.dev/skills/chrismckerracher/claude-dream-team/git-worktree"><img src="https://agentmods.dev/badge/skills/chrismckerracher/claude-dream-team/git-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 Git Worktree Management

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrismckerracher/claude-dream-team/git-worktree"><img src="https://agentmods.dev/badge/skills/chrismckerracher/claude-dream-team/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,299 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.00038 $0.01299
Opus 5 $0.00019 $0.00649
Sonnet 5 $0.00008 $0.00260
Haiku 4.5 $0.00004 $0.00130

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

Security

Grade A, and why

Git Worktree Management 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 9d 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.

dream-team-plugin/skills/git-worktree/SKILL.md · 176 lines

How it starts

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

Git Worktree Management

Git worktrees enable multiple coding agents to work on different tasks simultaneously without interfering with each other. Each agent gets its own working directory with its own branch.

Worktree Lifecycle

CREATE → WORK → SUBMIT → REVIEW → QA → MERGE → CLEANUP

1. Create Worktree

# From the main repo root
EPIC_BRANCH="epic/feature-name"
AGENT_NAME="coder-1"
TASK_ID="42"
TASK_SLUG="add-user-api"
WORKTREE_DIR="../worktrees/${AGENT_NAME}-task-${TASK_ID}"

# Create worktree from the epic branch
git worktree add "${WORKTREE_DIR}" "${EPIC_BRANCH}"

# Enter worktree and create feature branch
cd "${WORKTREE_DIR}"
git checkout -b "${AGENT_NAME}/${TASK_SLUG}"

2. Work in Worktree

# Stay in your worktree directory
cd "${WORKTREE_DIR}"

# Regular development workflow
# ... make changes ...
git add <specific-files>
git commit -m "feat(users): add user creation endpoint"

# Stay up to date with epic branch periodically
git fetch origin
git rebase "${EPIC_BRANCH}"

3. Submit for Review

# Ensure tests pass
npm test  # or project-specific command

# Push feature branch
git push -u origin "${AGENT_NAME}/${TASK_SLUG}"

# Update task status (via TaskUpdate tool, not git)

4. After Merge Approval

# Merge into epic branch (done by Team Lead or automation)
git checkout "${EPIC_BRANCH}"
git merge --no-ff "${AGENT_NAME}/${TASK_SLUG}"
git push origin "${EPIC_BRANCH}"

5. Cleanup

# Remove the worktree
cd /path/to/main/repo
git worktree remove "${WORKTREE_DIR}"

# Delete the feature branch (local and remote)
git branch -d "${AGENT_NAME}/${TASK_SLUG}"
git push origin --delete "${AGENT_NAME}/${TASK_SLUG}"

Branch Naming Convention

{agent-name}/{task-slug}

Examples:
  coder-1/add-user-api
  coder-2/fix-auth-middleware
  coder-1/update-payment-types

Worktree Directory Convention

project-root/
├── .git/                    # Main repo
├── src/                     # Main working directory
└── ../worktrees/            # Sibling directory for worktrees
    ├── coder-1-task-42/     # Agent 1's workspace
    ├── coder-2-task-43/     # Agent 2's workspace
    └── coder-1-task-44/     # Agent 1's next task

Read the full file on GitHub · 176 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. 9d ago First seen · 176 lines · 38 tokens per session scan A 4082f655f699

Subscribe to this mod's changes

Git Worktree Management is a skill published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,299 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

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens