git:worktrees

Manage parallel Git worktrees for multiple branches concurrently.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dalawwa/labor-methods --skill git-worktrees-dalawwa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git:worktrees
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/git/skills/worktrees
Command: npx skills add https://github.com/dalawwa/labor-methods --skill git-worktrees-dalawwa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git worktrees solve the problem of developing and testing across multiple branches in parallel without duplicating repositories or losing context.

Core Features & Use Cases

  • Create linked worktrees for ongoing features, hotfixes, or PR reviews while keeping the main working directory clean.
  • Switch contexts by changing directories, enabling side-by-side testing and comparison of implementations across branches.
  • Manage worktree lifecycle with commands like git worktree add, list, move, lock, unlock, prune, and repair.

Quick Start

Create a worktree for a feature branch from main and start development in the new directory.

Frequently Asked Questions about git:worktrees

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 stashing changes?

Git worktrees allow you to run multiple branches concurrently in separate directories, enabling parallel feature development and side-by-side testing without stashing or losing context.

What is the best way to set up a Git worktree for an isolated feature branch?

To set up a Git worktree, use the git worktree add command to create a linked directory for your feature branch, keeping the main working directory clean while starting development immediately.

Can I use Git worktrees for side-by-side testing across different versions?

Yes, Git worktrees enable side-by-side testing by allowing you to switch contexts simply by changing directories, letting you compare implementations across multiple branches concurrently.

How do I safely remove a Git worktree after finishing a code review?

Safely remove a Git worktree using the git worktree remove command, followed by git worktree prune to clean up any stale administrative files left in the main repository.

When should I lock a Git worktree during parallel development?

Lock a Git worktree using git worktree lock when the linked directory is on a portable or network drive, preventing automatic pruning from deleting or moving the working tree unexpectedly.