worktree

A workflow for creating and managing Git worktrees, which are separate working directories linked to different branches of the same repository.

In plain words
What is it for?
Use it to create a new branch in a separate directory, check existing worktrees, and follow a consistent location for parallel development.
Why use it?
It lets developers work on multiple branches at once without repeatedly switching branches or stashing changes.

Skill for Claude CodeCodex

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/forrestchang/worktree-workflow/worktree
Any agent
npx skills add forrestchang/worktree-workflow --skill worktree
Clone the repo
git clone --depth 1 https://github.com/forrestchang/worktree-workflow

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,361 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00030 $0.01361
Opus 5 $0.00015 $0.00681
Sonnet 5 $0.00006 $0.00272
Haiku 4.5 $0.00003 $0.00136

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

Security

Grade C, and why

worktree scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$worktrees_dir/${repo_name}-${dir_safe_branch}"
skills/worktree/SKILL.md · 183 lines

How it starts

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

Git Worktree Workflow

Create a git worktree to enable parallel development on multiple branches.

Arguments

  • First argument: New branch name (required)
  • Second argument: Base branch to create from (optional, auto-detects default branch)

Worktree Directory Convention

Worktrees are created in ../worktrees/<repo-name>-<branch-name> relative to the main repository.

This naming convention:

  • Keeps all worktrees in a shared worktrees directory above the repo
  • Includes repo name to avoid conflicts when working on multiple projects
  • Includes branch name for easy identification

Example: If working in /home/user/projects/my-app on branch feature-auth, the worktree path would be /home/user/projects/worktrees/my-app-feature-auth

Instructions

  1. Get repository info

    # Get repo root and name
    repo_root=$(git rev-parse --show-toplevel)
    repo_name=$(basename "$repo_root")
    
  2. Check repository status

    git status
    git worktree list
    
  3. Determine base branch

    • Use the second argument if provided
    • Otherwise, detect default branch:
      # Try remote HEAD first
      git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
      # Fallback to checking main/master
      git show-ref --verify --quiet refs/remotes/origin/main && echo "main"
      git show-ref --verify --quiet refs/remotes/origin/master && echo "master"
      
  4. Create the worktree

    # Define paths
    branch_name="<first-argument>"
    # Convert slashes in branch name to dashes for directory name
    # e.g., "feature/user-auth" -> "feature-user-auth"
    dir_safe_branch="${branch_name//\//-}"
    worktrees_dir="$(dirname "$repo_root")/worktrees"
    worktree_path="$worktrees_dir/${repo_name}-${dir_safe_branch}"
    
    # Create worktrees directory if needed
    mkdir -p "$worktrees_dir"
    
    # Fetch latest from base branch
    git fetch origin <base-branch>
    
    # Create worktree with new branch from base
    git worktree add "$worktree_path" -b "$branch_name" origin/<base-branch>
    

Read the full file on GitHub · 183 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 · 183 lines · 30 tokens per session scan C 3d311d6ed341

Subscribe to this mod's changes

worktree is a skill published in the GitHub repository forrestchang/worktree-workflow (109 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 1,361 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens