git-worktree

Create, list, switch, and clean Git worktrees with symlinked .env files.

1|Updated Feb 6, 2026

Search Tags:#git #workflow #development #version control #branching #worktree

Ready to run

npx skills add https://github.com/skinnyandbald/fish-skills --skill git-worktree-skinnyandbald

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/skinnyandbald/fish-skills/tree/main/skills/git-worktree
Command: npx skills add https://github.com/skinnyandbald/fish-skills --skill git-worktree-skinnyandbald

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of Git worktrees, allowing developers to isolate branches for parallel development without the complexity of manual setup and cleanup.

Core Features & Use Cases

Create Worktrees: Easily create new Git worktrees for feature branches or hotfixes, with options to specify a base branch.
Symlinked .env: Automatically symlinks the project's .env file into new worktrees, ensuring a single source of truth for environment variables.
Cleanup: Safely remove inactive worktrees to keep your project tidy.
Use Case: When starting a new feature, you can create a dedicated worktree for it, keeping your main branch clean and allowing you to switch contexts seamlessly.

Quick Start

Use the git-worktree skill to create a new worktree for a feature branch named 'new-feature'.

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 development without manual setup?▼

Git worktree management automates creating isolated worktrees for parallel branch development. It handles directory creation and symlinks environment files automatically, keeping your main branch clean while allowing seamless context switching between features.

How does Git worktree handle environment configuration across isolated branches?▼

Git worktree automatically symlinks your project's .env file into newly created worktrees. This ensures a single source of truth for environment variables, maintaining consistent configuration across all isolated parallel development branches.

What is the best way to create a Git worktree for a feature branch?▼

Creating a Git worktree for a feature branch involves using dedicated management commands to set up an isolated directory. You can specify a base branch, and the tool automatically configures symlinks and handles project conventions.

How do I safely clean up and remove inactive Git worktrees?▼

Cleaning up inactive Git worktrees involves using safe removal commands provided by the management tool. This ensures your project directory remains tidy without risking damage to active branches or losing uncommitted changes in other worktrees.

Can I switch between Git worktrees without manually changing directories?▼

Switching between Git worktrees is supported natively by the management tool. It allows you to seamlessly transition contexts between isolated parallel development branches without manually navigating the file system.

When should I use Git worktrees instead of standard branching?▼

Git worktrees are ideal when you need isolated parallel development workflows without stashing changes. They allow you to work on multiple branches simultaneously in separate directories, perfect for starting new features or hotfixes while keeping your main branch clean.