start-worktree

Create git worktrees as sibling directories for parallel branch development.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill start-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-worktree
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/start-worktree
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill start-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set up git worktrees to work on multiple branches in parallel without stashing or losing in-progress changes. This enables you to switch contexts quickly, test changes side-by-side, and keep long-running work isolated from your main branch.

Core Features & Use Cases

  • Separate working directories that share the same git history, allowing parallel development.
  • Quick context switching between branches without stashing or commit churn.
  • Safe cleanup and maintenance using the provided git worktree commands.

Quick Start

Create a new worktree for a target branch using git worktree add according to the Setup guidelines.

Frequently Asked Questions about start-worktree

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

FAQPage Schema
How do I work on multiple git branches in parallel without stashing changes?

Git worktrees let you work on multiple branches in parallel by creating separate working directories that share the same git history, eliminating the need to stash or commit in-progress changes when switching contexts.

When should I use git worktrees for parallel development?

Git worktrees are useful for hotfixes, feature work, PR reviews, and running tests across branches in parallel. They isolate long-running work from your main branch while enabling quick side-by-side context switching.

What's the best way to set up a git worktree for a new feature branch?

You can set up a git worktree by using the git worktree add command, which creates a sibling directory for the target branch. This allows you to manage isolated development environments without affecting your main working directory.

Does using git worktrees require stashing my current uncommitted work?

No, git worktrees are designed specifically to avoid stashing. Each worktree operates as an independent working directory with shared history, so you can leave uncommitted changes intact in one branch while starting new work in another.

How do I safely clean up and remove git worktrees after merging a branch?

You can safely clean up and remove worktrees using the provided git worktree management commands. These commands ensure the sibling directories are deleted properly without disrupting the shared repository history or your main working directory.