using-git-worktrees

Creates, lists, removes, locks, unlocks, prunes, and cleans Git worktrees for concurrent branches.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill using-git-worktrees-changoo89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/using-git-worktrees
Command: npx skills add https://github.com/changoo89/claude-pilot --skill using-git-worktrees-changoo89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolated workspaces enable parallel feature development by preventing conflicts across branches and reducing context switching.

Core Features & Use Cases

  • Isolated git worktrees for concurrent branches
  • Simple switch, list, and prune workflows
  • Safe cleanup after merging features

Quick Start

Create a new worktree for each feature with git worktree add and switch between worktrees as you develop.

Frequently Asked Questions about using-git-worktrees

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

FAQPage Schema
How do I use git worktrees for parallel branch development?

Git worktrees provision isolated workspaces for concurrent branches, allowing you to develop multiple features simultaneously. You can create a new worktree for each feature using git worktree add and safely switch between them without disturbing the main branch.

What is the best way to run long-running tests on one branch while developing another?

Git worktrees provide isolated workspaces for concurrent branches, letting you execute long-running tests in one worktree while actively developing in another. This prevents context switching and allows parallel tasks to proceed without interrupting your main development workflow.

How do I safely clean up and prune git worktrees after merging a feature?

You can safely clean up git worktrees after merging features using built-in pruning and removal workflows. The process involves removing the isolated worktree directory and pruning stale references to maintain a cohesive branch management workflow without leaving orphaned branches.

Can I lock a git worktree to prevent accidental deletion during hotfixes?

Yes, git worktree management includes locking and unlocking functionality to prevent accidental removal. This is particularly useful when performing hotfixes or running experiments, ensuring your isolated workspaces remain secure until you explicitly unlock and prune them.

Does working with isolated git worktrees reduce context switching across feature branches?

Yes, isolated git worktrees reduce context switching by provisioning separate workspaces for concurrent branches. Instead of constantly switching branches in a single directory, you navigate between worktrees, allowing each feature to maintain its own independent state.