git-worktree

Git worktrees enable parallel development by checking out multiple branches simultaneously from a single repository. They share one .git directory across separate working trees, eliminating the overhead of repeated clones and frequent checkouts for parallel feature work.

Using git worktree automates managing multiple working directories for parallel workflows like PR reviews and feature development. You can create, list, move, and prune separate working trees while sharing a single .git directory to avoid duplicating clones.

You can create a worktree for a specified branch in an adjacent directory and start working there immediately. The Skill supports creating, moving, removing, locking, and pruning worktrees to streamline repository management and maintenance workflows.

Yes, git worktrees share a single .git directory while keeping separate working trees for each checked-out branch. This space-efficient workflow enables parallel development without duplicating repository data or requiring multiple full clones.

Yes, you can use it for maintenance workflows to create, list, move, prune, and repair worktrees. This streamlines repository management by automating the cleanup and organization of working directories tied to a single shared .git directory.

You should avoid git worktree if your parallel development workflow requires complete repository isolation rather than sharing a single .git directory. If your repository management needs independent clones without shared references, worktrees may introduce unwanted coupling between branches.