git-worktree

Git worktrees let you create isolated branch environments in separate directories. Instead of switching branches repeatedly, you can work on multiple branches simultaneously by creating a worktree for each feature, keeping your main checkout clean and avoiding merge conflicts.

Create a worktree by specifying a base branch, deriving a branch name from your feature description or PR number with appropriate prefixes, then running the creation command to place it at ./trees/{branch-name}. The Skill automates naming conventions and location management.

Worktrees enable parallel branch development by storing each branch in a dedicated ./trees/ subdirectory. This approach isolates work, eliminates branch-switching overhead, and lets you maintain separate build states and dependencies for each feature simultaneously.

Yes. Git worktrees are designed to let you work on multiple PRs and feature branches concurrently. The Skill proactively detects when you reference a PR or start a new feature, then creates an isolated worktree so you can develop without interrupting other work.

The Skill provides cleanup and lifecycle management steps to remove worktrees you no longer need and prune their associated branches. This keeps your repository organized and frees up disk space after features are merged or abandoned.

Worktree creation requires selecting a base branch (typically main or develop) and defining a branch name with appropriate prefixes. The Skill handles deterministic naming conventions and fetches remote refs to ensure the base branch exists before creating the worktree.