worktree-management

Automate Git worktree creation with isolated Docker services and port allocation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill worktree-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worktree-management
Source: https://github.com/arlenagreer/claude_configuration_docs/tree/main/skills/worktree-management
Command: npx skills add https://github.com/arlenagreer/claude_configuration_docs --skill worktree-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, git, jq, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Managing multiple development branches often leads to environment conflicts, port clashes, and complex setup. This skill automates the creation and management of Git worktrees, providing completely isolated development environments with dedicated Docker services and browser automation, allowing you to work on multiple features or bug fixes simultaneously without interference.

Core Features & Use Cases

  • Automated Worktree Creation: Instantly sets up new Git worktrees with unique Docker Compose configurations and auto-allocated ports.
  • Isolated Browser Automation: Ensures each worktree has its own browser profiles and debugging ports, preventing conflicts during parallel E2E testing.
  • Conflict-Free Development: Automatically handles port allocation, environment file copying, and Docker service isolation, so you can switch contexts seamlessly and avoid setup headaches.
  • Use Case: Need to work on a new feature while a critical bug fix is in progress? Create a worktree for each. This skill ensures both environments run independently, with their own databases and browser sessions, eliminating setup headaches and context switching friction.

Quick Start

Example: Create a new worktree for a feature

@worktree create feature-user-export

Example: Create a worktree and start its services

@worktree create docs-api --branch=docs/api-documentation --start-services

Example: List all active worktrees

@worktree list

Frequently Asked Questions about worktree-management

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

FAQPage Schema
How do I manage multiple Git branches without port conflicts and environment clashes?▼

Git worktree management automates the creation of isolated development environments, each with dedicated ports, Docker services, and browser profiles. This lets you work on multiple branches simultaneously without interference or manual setup.

Can I run parallel development sessions on different branches with separate Docker containers?▼

Yes. Worktree management provisions each branch with its own Docker Compose configuration, auto-allocated ports, and isolated MCP instances, enabling true parallel development without service conflicts or port collisions.

How do I set up automatic port allocation across multiple worktrees?▼

Worktree automation handles port allocation by creating unique port mappings for each worktree's Docker services. Environment files are copied from the main project and extended per-worktree, eliminating manual port assignment.

What's the best way to handle browser automation across multiple feature branches?▼

Each worktree gets isolated browser profiles and debugging ports, preventing conflicts during parallel E2E testing. This ensures independent browser sessions across branches without cross-contamination.

Do I need Docker and Git installed to use worktree-based isolated environments?▼

Yes. Worktree management requires Git for branch handling and Docker for service isolation. The skill also depends on jq for JSON processing and uses scripts to automate configuration and port management.

Can worktree isolation handle environment file copying and CORS configuration automatically?▼

Yes. The skill automatically copies environment files from your main project to each worktree and applies per-worktree CORS configuration, eliminating manual environment setup for isolated development contexts.