New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git Worktrees

by jamesrochabrun in jamesrochabrun/skills

Manage Git worktrees for parallel Claude Code development. An agent skill from jamesrochabrun/skills.

MITAuto-check passedDevelopment

Install Git Worktrees

skills CLI
$ npx skills add jamesrochabrun/skills --skill git-worktrees -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jamesrochabrun/skills git-worktrees --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/git-worktrees .claude/skills/git-worktrees && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-worktrees
GitHub stars
215
Token cost
~4.2k tokens
SKILL.md length
1,358 words
Files
8 (incl. scripts, references)
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Manage Git worktrees for parallel Claude Code development. An agent skill from jamesrochabrun/skills.

  • Works in 10 steps: Create a New Worktree (Super Easy!) → View All Worktrees → Clean Up Old Worktrees → …
  • Engineers ask to create a worktree
  • SKILL.md covers Overview, Quick Start, Core Workflow and Essential Scripts, plus 3 more sections
  • Runs Shell scripts from its folder; calls git

What it does

Git Worktrees is an agent skill from jamesrochabrun/skills. Manage Git worktrees for parallel Claude Code development. Use this skill when engineers ask to "create a worktree", "run parallel Claude sessions", "work on multiple features simultaneously", or need help with worktree management.

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/best_practices.md`, `references/slash_command_template.md` and `references/worktree_commands.md`).

It sits in Development, covering Git worktrees. The licence is MIT.

When your agent uses it

  • Engineers ask to create a worktree
  • Run parallel Claude sessions
  • Work on multiple features simultaneously
  • Need help with worktree management

Example prompts

  • “create a worktree”
  • “run parallel Claude sessions”
  • “work on multiple features simultaneously”
  • “/git-worktrees”

Requirements

  • A Bash shell

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Create a New Worktree (Super Easy!)
  2. View All Worktrees
  3. Clean Up Old Worktrees
  4. Name Worktrees Descriptively
  5. Always Run /init
  6. Merge Frequently
  7. Clean Up Weekly
  8. Use Scripts
  9. Monitor Progress
  10. Limit Concurrent Sessions

What it can do on your machine

Read from SKILL.md and the folder at commit 2482c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Worktrees loads about 4.2k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 1,358 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jamesrochabrun/skills at commit 2482c17, republished under its MIT licence (© jamesrochabrun). 1,358 words, ~4,183 tokens.

Download SKILL.mdSave it as .claude/skills/git-worktrees/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
git-worktrees
description
Manage Git worktrees for parallel Claude Code development. Use this skill when engineers ask to "create a worktree", "run parallel Claude sessions", "work on multiple features simultaneously", or need help with worktree management.

Git Worktrees for Claude Code

Overview

Run multiple Claude Code sessions in parallel on different branches using Git worktrees. This skill provides simple scripts and workflows to set up, manage, and clean up worktrees, enabling true parallel development without conflicts.

Why Worktrees?

  • Parallel Development: Run multiple Claude Code instances simultaneously
  • Zero Conflicts: Each worktree has independent file state
  • Fast Context Switching: No need to stash/commit when switching tasks
  • Isolated Experiments: Try different approaches without affecting main work
  • Long-Running Tasks: Let Claude work in background while you continue in main

Quick Start

1. Create a New Worktree (Super Easy!)

Just run the interactive script:

bash
scripts/create_worktree.sh

This will:

  • ✅ Prompt for feature name
  • ✅ Create a new branch
  • ✅ Set up the worktree
  • ✅ Open in VS Code / editor
  • ✅ Give you the Claude Code setup command

That's it! The script handles all complexity.

2. View All Worktrees
bash
scripts/list_worktrees.sh

Shows a clean, formatted list of all your worktrees with their branches and status.

3. Clean Up Old Worktrees
bash
scripts/cleanup_worktrees.sh

Interactive removal of merged or abandoned worktrees.

Core Workflow

Pattern 1: Parallel Feature Development

Scenario: You want Claude to build feature A while you work on feature B.

Steps:

  1. Create worktree for feature A:

    bash
    scripts/create_worktree.sh
# Enter: feature-a
# Script creates: ../repo-feature-a/

  2. Open Claude Code in the new worktree:

    • The script outputs the path
    • Open Claude Code and navigate to that directory
    • Run /init to orient Claude

  3. Give Claude the task:

    "Build the user authentication feature with OAuth support"

  4. Continue your work in main:

    • Your original directory is unchanged
    • No conflicts, no waiting
    • Claude works in parallel

  5. When both are done, merge:

    bash
    # Review Claude's work
cd ../repo-feature-a
git log

# If good, merge back
git checkout main
git merge feature-a

# Clean up
scripts/cleanup_worktrees.sh
Pattern 2: Long-Running Refactor

Scenario: You want Claude to refactor a large module while you continue development.

Steps:

  1. Create refactor worktree:

    bash
    scripts/create_worktree.sh
# Enter: refactor-auth-module

  2. Start Claude in refactor worktree:

    "Refactor the authentication module to use dependency injection"

  3. Continue your daily work in main:

    • No interruption
    • No merge conflicts
    • Check progress periodically

  4. Review and integrate when ready:

    bash
    cd ../repo-refactor-auth-module
git log --oneline
# Review changes

# Merge when satisfied
git checkout main
git merge refactor-auth-module
Pattern 3: Multiple AI Agents (Advanced)

Scenario: You want 3 Claude instances working on different features simultaneously.

Steps:

  1. Create 3 worktrees:

    bash
    scripts/create_worktree.sh  # feature-api-endpoints
scripts/create_worktree.sh  # feature-ui-dashboard
scripts/create_worktree.sh  # feature-email-notifications

  2. Open 3 Claude Code sessions:

    • Session 1: ../repo-feature-api-endpoints/
    • Session 2: ../repo-feature-ui-dashboard/
    • Session 3: ../repo-feature-email-notifications/

  3. Assign tasks to each Claude:

    • Claude 1: "Build REST API endpoints for user management"
    • Claude 2: "Create admin dashboard UI"
    • Claude 3: "Implement email notification system"

  4. Monitor progress:

    bash
    scripts/list_worktrees.sh

  5. Merge features as they complete:

    bash
    # Feature by feature
git checkout main
git merge feature-api-endpoints
git merge feature-ui-dashboard
git merge feature-email-notifications

# Clean up
scripts/cleanup_worktrees.sh
Pattern 4: Hotfix While Development Continues

Scenario: Production bug needs immediate fix while Claude is working on a feature.

Steps:

  1. Claude is already working in a feature worktree

    • Let it continue, don't interrupt

  2. Create hotfix worktree from main:

    bash
    scripts/create_worktree.sh
# Enter: hotfix-login-bug
# Choose base branch: main

  3. Fix the bug yourself or with another Claude session:

    bash
    cd ../repo-hotfix-login-bug
# Make fixes
git add .
git commit -m "Fix login redirect bug"

  4. Merge hotfix to main:

    bash
    git checkout main
git merge hotfix-login-bug
git push origin main

  5. Sync feature worktree with latest main:

    bash
    cd ../repo-feature-xyz
scripts/sync_worktree.sh
# Merges latest main into feature branch

Essential Scripts

scripts/create_worktree.sh

Interactive worktree creation with all the right defaults.

What it does:

  1. Prompts for feature name
  2. Validates git repo
  3. Creates branch from main (or specified base)
  4. Sets up worktree in parallel directory
  5. Outputs setup instructions

Usage:

bash
scripts/create_worktree.sh

# Prompts:
# Feature name: my-feature
# Base branch (default: main):
#
# Creates: ../repo-my-feature/
# Branch: my-feature

Advanced usage:

bash
# Create from specific branch
scripts/create_worktree.sh --base develop

# Specify location
scripts/create_worktree.sh --dir ~/worktrees/my-feature
scripts/list_worktrees.sh

Shows all active worktrees with status.

Output:

╔════════════════════════════════════════════════╗
║            Active Git Worktrees                ║
╚════════════════════════════════════════════════╝

📁 Main Worktree
   Path: /home/user/project
   Branch: main
   Status: clean

📁 Feature Worktrees
   Path: /home/user/project-feature-api
   Branch: feature-api
   Status: 2 uncommitted changes

   Path: /home/user/project-refactor
   Branch: refactor-auth
   Status: clean
scripts/cleanup_worktrees.sh

Interactive cleanup of old worktrees.

Features:

  • Lists all worktrees with merge status
  • Identifies merged branches (safe to remove)
  • Prompts for confirmation
  • Safely removes worktree and branch

Usage:

bash
scripts/cleanup_worktrees.sh

# Output:
# Found 3 worktrees
#
# 1. feature-api (merged to main) - Safe to remove
# 2. feature-dashboard (not merged) - Keep
# 3. old-experiment (not merged, 30 days old) - Consider removing
#
# Which worktrees to remove? (1,3): 1
scripts/sync_worktree.sh

Keep worktree up-to-date with main branch.

What it does:

  1. Fetches latest from remote
  2. Merges main into current worktree branch
  3. Handles conflicts with guidance

Usage:

bash
# From within a worktree
cd ../repo-feature-api
scripts/sync_worktree.sh

# Or specify worktree
scripts/sync_worktree.sh ../repo-feature-api

Claude Code Integration

Important: Run /init in Each Worktree

When you open a new Claude Code session in a worktree, always run /init first:

/init

This ensures Claude:

  • Understands the codebase structure
  • Has proper context
  • Can navigate files correctly
  1. Create worktree (using script)
  2. Open Claude Code in worktree directory
  3. Run /init to orient Claude
  4. Give task to Claude
  5. Monitor via git log or file watching
  6. Review when complete
  7. Merge if satisfied
  8. Cleanup worktree

Best Practices

Naming Conventions

Good names:

  • feature-user-auth ✅
  • refactor-api-layer ✅
  • hotfix-login-bug ✅
  • experiment-new-db ✅

Bad names:

  • test ❌ (too vague)
  • wt1 ❌ (meaningless)
  • fixes ❌ (unclear)

Recommended format:

<type>-<short-description>

Types:
- feature-*
- refactor-*
- hotfix-*
- experiment-*
- review-*
Directory Structure

Recommended layout:

~/projects/
  └── myapp/              # Main worktree (main branch)
      ├── myapp-feature-api/      # Feature worktree
      ├── myapp-refactor-auth/    # Refactor worktree
      └── myapp-hotfix-bug/       # Hotfix worktree

The scripts default to creating worktrees as siblings to your main directory with a naming pattern: <repo>-<branch-name>.

When to Use Worktrees

✅ Use worktrees when:

  • Running multiple Claude Code sessions in parallel
  • Working on independent features simultaneously
  • Doing long-running refactors
  • Experimenting with major changes
  • Quick hotfixes during feature development
  • Code reviews without interrupting work

❌ Don't use worktrees for:

  • Simple branch switching (just use git checkout)
  • Minor tweaks (stash instead)
  • Single-task workflows
  • Very short-lived branches (< 1 hour)
Keeping Worktrees in Sync

Problem: Feature branches can get out of date with main.

Solution: Regularly sync worktrees:

bash
# Option 1: Use the sync script
cd ../repo-feature-api
scripts/sync_worktree.sh

# Option 2: Manual sync
cd ../repo-feature-api
git fetch origin
git merge origin/main

Recommended frequency:

  • Daily for long-running features
  • After major merges to main
  • Before creating PRs
Managing Many Worktrees

Quick status of all worktrees:

bash
scripts/list_worktrees.sh

Regular cleanup (weekly):

bash
scripts/cleanup_worktrees.sh

Find stale worktrees:

bash
# Worktrees with old commits
git worktree list | while read path branch commit; do
  cd "$path"
  last_commit=$(git log -1 --format=%cr)
  echo "$branch: Last commit $last_commit"
done

Troubleshooting

Show full SKILL.md (618 more words)Show less
Issue: "fatal: invalid reference"

Cause: Branch name has invalid characters

Solution: Use alphanumeric + hyphens only:

bash
# Bad
feature/my_feature  ❌

# Good
feature-my-feature  ✅
Issue: "cannot remove worktree, path is not a working tree"

Cause: Worktree directory was manually deleted

Solution: Prune worktree references:

bash
git worktree prune
Issue: Claude seems "lost" in worktree

Cause: Didn't run /init after opening worktree

Solution: Always run /init when starting Claude in a new worktree:

/init
Issue: Merge conflicts when syncing worktree

Cause: Changes in worktree conflict with main

Solution 1: Resolve conflicts manually:

bash
cd ../repo-feature-api
git fetch origin
git merge origin/main
# Fix conflicts in editor
git add .
git commit -m "Merge main and resolve conflicts"

Solution 2: If you want to discard worktree changes and restart:

bash
cd ../repo-feature-api
git fetch origin
git reset --hard origin/main
# Start feature over
Issue: "Cannot lock ref" error

Cause: Branch exists in multiple worktrees

Solution: You can't have the same branch checked out in multiple worktrees. Create a new branch:

bash
scripts/create_worktree.sh
# Use a different branch name
Issue: Worktree takes up too much disk space

Cause: Git worktrees share the .git directory, but files are duplicated

Solution 1: Clean up old worktrees:

bash
scripts/cleanup_worktrees.sh

Solution 2: For large repos, use sparse-checkout:

bash
git -C ../repo-feature-api sparse-checkout set src/ tests/

Advanced Usage

Custom Slash Command

Create a /worktree command for Claude Code. See references/slash_command_template.md for the complete setup.

Usage after setup:

/worktree feature-new-api

Claude will:

  1. Create the worktree
  2. Provide setup instructions
  3. Offer to continue the conversation in the new worktree
Sharing Worktrees in Team

Worktrees are local only, but you can share the workflow:

  1. Share branch, not worktree:

    bash
    cd ../repo-feature-api
git push origin feature-api

# Teammate creates their own worktree
git worktree add ../repo-feature-api feature-api

  2. Document your worktree structure in team docs

  3. Use consistent naming across team

Worktree Performance Optimization

For large repos:

  1. Use sparse-checkout (only checkout files you need):

    bash
    git -C ../repo-feature-api sparse-checkout init
git -C ../repo-feature-api sparse-checkout set src/ tests/

  2. Use worktree prune regularly:

    bash
    git worktree prune

  3. Limit concurrent worktrees to 3-5 for best performance

Common Workflows Summary

Quick Reference
TaskCommand
Create new worktreescripts/create_worktree.sh
List all worktreesscripts/list_worktrees.sh
Clean up worktreesscripts/cleanup_worktrees.sh
Sync with mainscripts/sync_worktree.sh
Manual creategit worktree add ../path branch-name
Manual listgit worktree list
Manual removegit worktree remove ../path
Prune referencesgit worktree prune

Real-World Examples

Example 1: Parallel API & UI Development

Setup:

bash
# Create API worktree
scripts/create_worktree.sh
# Name: feature-api

# Create UI worktree
scripts/create_worktree.sh
# Name: feature-ui

Execution:

  • Claude 1 in ../repo-feature-api: "Build REST API for user management"
  • Claude 2 in ../repo-feature-ui: "Create React UI for user management"
  • You in main: Continue other work

Merge:

bash
git checkout main
git merge feature-api
git merge feature-ui
scripts/cleanup_worktrees.sh
Example 2: Code Review Without Context Switching

Scenario: Need to review PR while Claude works on feature

Setup:

bash
# Claude is working in feature worktree
# You need to review PR #123

scripts/create_worktree.sh
# Name: review-pr-123
# Base: pr-branch-name

Execution:

  • Review code in ../repo-review-pr-123
  • Claude continues work in ../repo-feature-xyz
  • No context switching needed

Cleanup:

bash
# After review
scripts/cleanup_worktrees.sh
# Select review-pr-123
Example 3: Experimentation Without Risk

Scenario: Want to try a radical refactor without breaking current work

Setup:

bash
scripts/create_worktree.sh
# Name: experiment-new-architecture

Execution:

  • Experiment freely in ../repo-experiment-new-architecture
  • Main worktree remains stable
  • If experiment fails, just delete worktree

Decision:

bash
# If experiment succeeded
git checkout main
git merge experiment-new-architecture

# If experiment failed
scripts/cleanup_worktrees.sh
# Delete experiment worktree (no harm done)

Tips for Maximum Productivity

1. Name Worktrees Descriptively
  • You'll thank yourself later when you have 5 worktrees open
2. Always Run /init
  • First thing when opening Claude in a new worktree
3. Merge Frequently
  • Don't let worktrees diverge for weeks
  • Sync with main regularly
4. Clean Up Weekly
  • Run scripts/cleanup_worktrees.sh every Friday
  • Keep your workspace tidy
5. Use Scripts
  • Don't memorize git worktree commands
  • Scripts handle edge cases and validation
6. Monitor Progress
  • Use scripts/list_worktrees.sh to see what's active
  • Check git logs in worktrees periodically
7. Limit Concurrent Sessions
  • 3-5 worktrees max for best performance
  • More than that gets hard to manage

Resources

Scripts
  • create_worktree.sh - Interactive worktree creation
  • list_worktrees.sh - Show all active worktrees
  • cleanup_worktrees.sh - Remove old worktrees
  • sync_worktree.sh - Keep worktrees synchronized
References
  • worktree_commands.md - Complete Git worktree command reference
  • best_practices.md - Detailed best practices and patterns
  • slash_command_template.md - Create custom /worktree command

Summary

Git worktrees enable true parallel development with Claude Code:

✅ Run multiple Claude sessions without conflicts ✅ Switch contexts instantly without stashing ✅ Experiment safely without breaking main ✅ Simple scripts handle all complexity ✅ Clean workflows for common scenarios

Get started:

bash
scripts/create_worktree.sh

That's it! The scripts make worktrees simple and practical.

© jamesrochabrun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references) in skills/git-worktrees of jamesrochabrun/skills.

  • SKILL.md
  • references/best_practices.md
  • references/slash_command_template.md
  • references/worktree_commands.md
  • scripts/cleanup_worktrees.sh
  • scripts/create_worktree.sh
  • scripts/list_worktrees.sh
  • scripts/sync_worktree.sh

Open the folder on GitHubat commit 2482c17

Compare with similar skills

Git Worktrees next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Worktrees compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Worktrees this skilljamesrochabrun/skills215—~4.2kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Nagentdavidondrej/skills4.1k—~1.7kAutomated safety check: NotesMIT
Git Worktree IsolationjnMetaCode/superpowers-zh8.3k1 repos~982Automated safety check: PassMIT
WorktreeAgentsMesh/AgentsMesh2.4k—~553Automated safety check: NotesCustom licence
Cursor Composer Task DelegateChachamaru127/claude-code-harness3.2k—~4.4kAutomated safety check: NotesMIT

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Nagent

    davidondrej/skills

    Launch a new bb worker thread with the right project, model, worktree, and task brief.

    4.1k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Git Worktree Isolation

    jnMetaCode/superpowers-zh

    Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.

    8.3k GitHub starsUsed in 1 repo~982 tokens
    DevelopmentAuto-check passed

  • Worktree

    AgentsMesh/AgentsMesh

    Creates or reuses an isolated AgentsMesh Git worktree from a verified base branch, preserves existing changes, and optionally starts the worktree-scoped development environment.

    2.4k GitHub stars~553 tokensUpdated 14 days ago
    DevelopmentAuto-check: notes

  • Cursor Composer Task Delegate

    Chachamaru127/claude-code-harness

    Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.

    3.2k GitHub stars~4.4k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

  • Git Worktree Setup

    k8zdev/k8z

    Automate git worktree creation and copy private files (not tracked in git) to new workdirs.

    155 GitHub stars~930 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from jamesrochabrun/skills

All 23 skills in this repo

  • Prd Generator

    jamesrochabrun/skills

    Generate comprehensive Product Requirements Documents (PRDs) for product managers.

    215 GitHub starsUsed in 2 repos~3.8k tokens
    Auto-check passed

  • LLM Router

    jamesrochabrun/skills

    This skill should be used when users want to route LLM requests to different AI providers (OpenAI, Grok/xAI, Groq, DeepSeek, OpenRouter) using SwiftOpenAI-CLI.

    215 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed

  • Technical Launch Planner

    jamesrochabrun/skills

    Plan and execute technical product launches for developer tools, APIs, and technical products.

    215 GitHub starsUsed in 1 repo~3.8k tokens
    Auto-check passed

  • Design Brief Generator

    jamesrochabrun/skills

    Generate comprehensive design briefs for design projects. An agent skill from jamesrochabrun/skills.

    215 GitHub stars~3.3k tokensUpdated 8 mo ago
    Auto-check passed

  • Content Brief Generator

    jamesrochabrun/skills

    Generate comprehensive content briefs for writers, ensuring clarity, alignment, and strategic content creation across all formats.

    215 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

  • Swiftui Animation

    jamesrochabrun/skills

    This skill provides comprehensive guidance for implementing advanced SwiftUI animations, transitions, matched geometry effects, and Metal shader integration.

    215 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Categories

Questions about Git Worktrees

What does Git Worktrees do?

Manage Git worktrees for parallel Claude Code development. An agent skill from jamesrochabrun/skills. Git Worktrees is an agent skill from jamesrochabrun/skills. Manage Git worktrees for parallel Claude Code development.

When should I use Git Worktrees?

Git Worktrees fits situations like: engineers ask to create a worktree; run parallel Claude sessions; work on multiple features simultaneously; need help with worktree management.

How do I install Git Worktrees in Claude Code?

Run `npx skills add jamesrochabrun/skills --skill git-worktrees -a claude-code`. Or copy the skill folder (skills/git-worktrees in jamesrochabrun/skills) into .claude/skills/git-worktrees in your project. Claude Code loads it when a task matches its description.

How do I install Git Worktrees in Codex?

Run `npx skills add jamesrochabrun/skills --skill git-worktrees -a codex`. Or copy the skill folder (skills/git-worktrees in jamesrochabrun/skills) into .agents/skills/git-worktrees in your project. Codex loads it when a task matches its description.

Can I use Git Worktrees in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jamesrochabrun/skills --skill git-worktrees -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-worktrees, .gemini/skills/git-worktrees, .github/skills/git-worktrees and .opencode/skills/git-worktrees in your project.

What does Git Worktrees need to run?

Going by SKILL.md and its folder, Git Worktrees needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.

Does Git Worktrees access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Worktrees safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Git Worktrees use?

Git Worktrees is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Worktrees use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.8k tokens, read only when the agent opens those files.

What are the alternatives to Git Worktrees?

Skills that share tags, products or a category with Git Worktrees: Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars), Nagent (davidondrej/skills, 4.1k stars), Git Worktree Isolation (jnMetaCode/superpowers-zh, 8.3k stars) and Worktree (AgentsMesh/AgentsMesh, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Worktrees?

jamesrochabrun (a GitHub user) maintains it in jamesrochabrun/skills, which has 215 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on January 14, 2026.

Source: jamesrochabrun/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.