git-worktree

Create, list, switch, and clean up Git worktrees for parallel development.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill git-worktree-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/git-worktree
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill git-worktree-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, mise, direnv, and includes scripts (resource) components.

What problem does it solve?

This skill provides a centralized interface to manage Git worktrees, enabling isolated parallel development by creating, listing, switching, and cleaning up worktrees with guided prompts.

Core Features & Use Cases

  • Create worktrees from a base branch with clear branch-worktree naming
  • List all worktrees with status and current location
  • Switch between worktrees for parallel development
  • Clean up completed/unused worktrees with confirmation
  • Automatic management of a dedicated .worktrees directory and .gitignore
  • Optional env-file copying from the main repo to new worktrees
  • Optional integration with dev-tools trust (mise/direnv) for seamless workflows

Quick Start

Create a new worktree for a feature from main using the worktree-manager.sh script, then switch to it.

Frequently Asked Questions about git-worktree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Git worktrees for parallel feature branch development?▼

Manage Git worktrees for parallel feature branch development using a centralized script interface that creates, lists, switches, and cleans up isolated working directories. This prevents branch switching overhead and keeps multiple features active simultaneously.

How do I copy env-files when creating a new Git worktree?▼

Copy env-files when creating a new Git worktree through automatic env-file copying from the main repository to the new worktree directory. This ensures isolated branches maintain the necessary local configuration and environment variables.

Can I use mise and direnv with Git worktrees for environment trust integration?▼

Yes, you can use mise and direnv with Git worktrees through optional dev-tools trust integration. This setup provides seamless environment activation and dependency management across isolated parallel development branches.

What is the best way to clean up completed Git worktrees?▼

The best way to clean up completed Git worktrees is using a guided cleanup workflow with confirmation prompts. This safely removes unused worktrees and their associated branches while preventing accidental deletion of active development directories.

Do I need to manually configure a .worktrees directory and .gitignore?▼

You do not need to manually configure a .worktrees directory and .gitignore. The workflow automatically manages a dedicated directory for isolated worktrees and updates the .gitignore file to prevent committing working directories.

How do I switch between Git worktrees during parallel development?▼

Switch between Git worktrees during parallel development using a simple interface that lists all worktrees with their current location and status. This allows rapid context switching between multiple active feature branches.