Skill

git-worktree

Manages git worktrees via unified bash script for parallel development: creates isolated feature environments, lists/switches status, copies .env files, cleans up merged/stale worktrees.

Git

Bash

git-workflow

npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineer

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

Supporting Assets

scripts/worktree-manager.sh

SKILL.md

Similar Skills

git-worktree

Manages Git worktrees for parallel development: create from main with .env copying, list status, switch, cleanup interactively via bash script.

1 file

compound-engineering

git-worktree

Manages Git worktrees for isolated parallel development: creates from main branch, lists status, switches, cleans up with interactive interface. Auto-copies .env files and updates .gitignore.

1 file

lavra

worktree-kit

562

Manages git worktrees: create, list, switch, cleanup; copies .env files to worktrees. For parallel feature work, isolated reviews, clean workspaces.

1 file

flow

Stats

Parent Repo Stars33

Parent Repo Forks7

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Git Worktree Manager

Overview

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