worktree

Name: worktree
Availability: InStock
Author: Speednet

Automates creation, listing, and closing of Git worktrees with per-worktree isolation.

21|8|Updated Mar 9, 2026

Search Tags:#automation #git #devops #worktree #makefile #parallel-development #speedwave

Ready to run

npx skills add https://github.com/speednet-software/speedwave --skill worktree-speednet-software

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/worktree
Command: npx skills add https://github.com/speednet-software/speedwave --skill worktree-speednet-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel feature development often requires separate workspaces with isolated dependencies. This skill automates and orchestrates Git worktrees to enable multiple feature branches to be developed side-by-side without polluting the main environment.

Core Features & Use Cases

Create new worktrees with isolated dependency installs and port isolation.
List existing worktrees and their config to monitor active development.
Close and clean up worktrees, including stopping dev processes and pruning branches when you are done.
All commands are driven through the main Makefile to ensure consistent builds and avoid direct calls to cargo, npm, or npx.

Quick Start

Use the worktree command to create a new worktree, list current worktrees, or close a worktree, then start development via the Makefile targets.

Frequently Asked Questions about worktree

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

FAQPage Schema

How do I manage Git worktrees for parallel feature development without polluting my main environment?▼

Managing Git worktrees for parallel feature development is done by creating isolated workspaces with separate dependency installs and port assignments. This allows multiple feature branches to be developed side-by-side without polluting the main environment.

What is the best way to isolate dependencies and ports across multiple Git branches?▼

Isolating dependencies and ports across multiple Git branches is achieved by generating per-worktree .worktree.json configurations. Each worktree gets its own isolated dependency installation and coordinated port assignment to prevent conflicts.

How do I create, list, and close Git worktrees using a Makefile-driven workflow?▼

Creating, listing, and closing Git worktrees is automated through a Makefile-driven workflow that avoids direct calls to cargo, npm, or npx. You use the worktree command to manage the lifecycle and start development via Makefile targets.

Do I need to manually stop dev processes and prune branches when closing a worktree?▼

Closing a worktree does not require manual process stopping or branch pruning. The closing and cleanup process automatically stops dev processes and prunes branches when you are done with the feature.

Can I build MCP servers and install dependencies within an isolated worktree setup?▼

Building MCP servers and installing dependencies within an isolated worktree setup is supported. The automation parses arguments, generates configurations, installs dependencies, builds MCP servers, and guides users from setup to launch.

Why should I use a Makefile for consistent builds instead of calling npm or cargo directly in worktrees?▼

Using a Makefile for consistent builds in worktrees prevents environment drift by enforcing a unified workflow. All commands are driven through the main Makefile to ensure consistent builds and avoid direct calls to cargo, npm, or npx.