How do I install the Git Worktree skill?

Run npx skillmds@latest add majesticlabs-dev/git-worktree in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Worktree safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Worktree?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Worktree free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Worktree?

majesticlabs-dev (@majesticlabs-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Worktree by majesticlabs-dev — Agent Skill

Name: Git Worktree
Author: majesticlabs-dev

Git Worktree

Manage git worktrees for parallel development. Use when the user wants to work on multiple branches simultaneously, create isolated environments for features/fixes, or clean up completed worktrees.

majesticlabs-dev 06838d7 2 files · 19.0 KB Updated Sep 17, 2026

File contents

Git Worktree Manager

Overview

This skill provides a unified interface for managing git worktrees, enabling isolated parallel development. Worktrees allow you to have multiple branches checked out simultaneously in separate directories.

Key features:

Automatic .env file copying from main repo to new worktrees
Unified storage in .worktrees/ directory
Cleanup of merged and stale worktrees

When to Use This Skill

Creating isolated environments for feature development
Working on multiple branches simultaneously
Reviewing PRs without stashing current work
Cleaning up completed feature branches

Critical: Always Use the Manager Script

Always use the worktree-manager.sh script rather than raw git worktree commands. The script handles:

Automatic .env file copying to new worktrees
Consistent storage in .worktrees/ directory
Proper .gitignore management

Core Commands

All operations use the unified worktree-manager.sh script:

bash scripts/worktree-manager.sh <command> [options]

Create Worktree

worktree-manager.sh create <branch-name> [source-branch]

Creates a new worktree in .worktrees/<branch-name>. If the branch exists, it checks it out. If not, creates a new branch from the source (defaults to main/master).

List Worktrees

worktree-manager.sh list

Shows all worktrees with their branch, commit, and status (clean/dirty/missing).

Switch Worktree

worktree-manager.sh switch <branch-name|path>

Provides information for switching to a worktree by branch name or path.

Cleanup Worktrees

worktree-manager.sh cleanup [--force]

Identifies and removes:

Worktrees with merged branches
Worktrees with deleted remote branches
Missing worktree directories

Use --force to skip confirmation prompt.

Copy Environment Files

worktree-manager.sh copy-env [worktree-path|branch-name]

Copies .env* files (excluding .env.example) from the main repo to a worktree. Useful for:

Adding env files to existing worktrees created before this feature
Refreshing env files after main repo changes

If run inside a worktree without arguments, copies to current location.

Storage

Worktrees are stored in .worktrees/ within the repository root. This directory is automatically added to .gitignore.

Example Workflow

# Start new feature
worktree-manager.sh create feature-auth

# Work in the new worktree
cd .worktrees/feature-auth

# List all worktrees
worktree-manager.sh list

# When done, clean up
worktree-manager.sh cleanup

Troubleshooting

Missing .env files in existing worktrees

If you have existing worktrees created before the automatic env copying feature:

bash scripts/worktree-manager.sh copy-env feature-branch

Or from within the worktree directory:

bash scripts/worktree-manager.sh copy-env

---name: git-worktreedescription: Manage git worktrees for parallel development. Use when the user wants to work on multiple branches simultaneously, create isolated environments for features/fixes, or clean up completed worktrees.---# Git Worktree Manager## OverviewThis skill provides a unified interface for managing git worktrees, enabling isolated parallel development. Worktrees allow you to have multiple branches checked out simultaneously in separate directories.**Key features:**- Automatic `.env` file copying from main repo to new worktrees- Unified storage in `.worktrees/` directory- Cleanup of merged and stale worktrees## When to Use This Skill- Creating isolated environments for feature development- Working on multiple branches simultaneously- Reviewing PRs without stashing current work- Cleaning up completed feature branches## Critical: Always Use the Manager Script**Always use the worktree-manager.sh script** rather than raw `git worktree` commands. The script handles:- Automatic `.env` file copying to new worktrees- Consistent storage in `.worktrees/` directory- Proper `.gitignore` management## Core CommandsAll operations use the unified `worktree-manager.sh` script:```bashbash scripts/worktree-manager.sh <command> [options]```### Create Worktree```bashworktree-manager.sh create <branch-name> [source-branch]```Creates a new worktree in `.worktrees/<branch-name>`. If the branch exists, it checks it out. If not, creates a new branch from the source (defaults to main/master).### List Worktrees```bashworktree-manager.sh list```Shows all worktrees with their branch, commit, and status (clean/dirty/missing).### Switch Worktree```bashworktree-manager.sh switch <branch-name|path>```Provides information for switching to a worktree by branch name or path.### Cleanup Worktrees```bashworktree-manager.sh cleanup [--force]```Identifies and removes:- Worktrees with merged branches- Worktrees with deleted remote branches- Missing worktree directoriesUse `--force` to skip confirmation prompt.### Copy Environment Files```bashworktree-manager.sh copy-env [worktree-path|branch-name]```Copies `.env*` files (excluding `.env.example`) from the main repo to a worktree. Useful for:- Adding env files to existing worktrees created before this feature- Refreshing env files after main repo changesIf run inside a worktree without arguments, copies to current location.## StorageWorktrees are stored in `.worktrees/` within the repository root. This directory is automatically added to `.gitignore`.## Example Workflow```bash# Start new featureworktree-manager.sh create feature-auth# Work in the new worktreecd .worktrees/feature-auth# List all worktreesworktree-manager.sh list# When done, clean upworktree-manager.sh cleanup```## Troubleshooting### Missing .env files in existing worktreesIf you have existing worktrees created before the automatic env copying feature:```bashbash scripts/worktree-manager.sh copy-env feature-branch```Or from within the worktree directory:```bashbash scripts/worktree-manager.sh copy-env```

Frequently asked questions