git-worktree

Manage Git worktrees for parallel development workflows.

15|1|Updated Dec 4, 2025

Search Tags:#git #workflow #worktrees #branch-management #version-control #git-worktree #parallel-development

Ready to run

npx skills add https://github.com/FreePeak/ktme --skill git-worktree-freepeak

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktrees allow you to checkout multiple branches at the same time in different directories, enabling parallel development without stashing or switching branches.

Core Features & Use Cases

Create and manage multiple worktrees for feature, hotfix, or PR review workflows.
List, move, and prune worktrees for clean, separated development contexts.
Coordinate changes across worktrees while sharing the same repository, reducing context switching.

Quick Start

Create a new worktree for a feature branch by running git worktree add ../project-feature-a -b feature-a.

Frequently Asked Questions about git-worktree

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

FAQPage Schema

How do I work on multiple Git branches at the same time without switching?▼

You can work on multiple branches simultaneously by creating Git worktrees. Worktrees let you checkout different branches in separate directories, enabling parallel development without stashing or switching branches in a single repository.

What is the best way to review a pull request without stashing my current changes?▼

Using a Git worktree is an effective way to review pull requests without stashing. You can create a dedicated worktree for the PR branch, keeping your current working directory untouched while testing the proposed changes in isolation.

How do I create a new worktree for a feature branch?▼

To create a worktree for a feature branch, use the command `git worktree add ../project-feature-a -b feature-a`. This checks out the new branch into a separate directory, allowing you to start parallel development immediately.

Can I move, lock, or prune existing worktrees for branch management?▼

Yes, you can manage existing worktrees by moving them to new directories, locking them to prevent deletion, or pruning them to clean up stale references. These actions keep your parallel development contexts organized and separated.

How does cross-worktree coordination work when sharing the same repository?▼

Cross-worktree coordination allows you to manage changes across multiple worktrees while sharing the same underlying Git repository. This reduces context switching and ensures all branches stay synchronized without requiring duplicate clones.

When should I not use Git worktrees for parallel development?▼

You should avoid Git worktrees if your project relies on absolute paths or if your development environment lacks support for multiple active working directories. Worktrees share the same repository, so tools with strict single-root configurations may experience conflicts.