worktree

Manage Git worktrees for parallel agents with isolated workspaces.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --skill worktree-heman1033p-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/heman1033p-create/heman1033p-create.github.io/tree/main/.gemini/skills/worktree
Command: npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --skill worktree-heman1033p-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows are simplified by managing multiple worktrees for parallel agents, enabling isolated workspaces and safer concurrent development.

Core Features & Use Cases

  • List worktrees for a repository
  • Create a new agent worktree with a corresponding branch
  • Show the path and branch for a specific agent
  • Remove an agent worktree (and optionally its branch)

Quick Start

Create the first agent worktree using /worktree new to start parallel agents.

Frequently Asked Questions about worktree

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

FAQPage Schema
How do I set up isolated workspaces for parallel agents in a Git repository?

You can establish isolated workspaces for parallel agents by creating Git worktrees within your repository, allowing concurrent development to operate safely in separate directories without interference.

What is the best way to manage multiple Git worktrees for concurrent development?

Managing multiple Git worktrees for concurrent development involves listing available worktrees, creating new ones with dedicated branches, and removing them when agent tasks are complete to maintain a clean repository state.

Can I retrieve the specific path and branch associated with an agent worktree?

Yes, you can retrieve the exact path and associated branch for a specific agent worktree, enabling you to quickly locate and direct parallel agents to their correct isolated directories.

How do I remove an agent worktree and its associated branch when finished?

You can remove an agent worktree and optionally delete its associated branch simultaneously, ensuring that completed parallel agent tasks do not leave unused isolated workspaces behind.

Does this Git worktree approach enforce a specific directory structure for parallel agents?

Yes, this approach enforces flat sibling worktrees, ensuring all isolated workspaces for parallel agents reside side-by-side in a predictable directory structure for easier management.