worktree-manager-skill

Automate git worktree creation, listing, removal, and monitoring with isolated ports.

3|1|Updated Nov 14, 2025

Search Tags:#automation #git #worktree #parallel #ports #dev

Ready to run

npx skills add https://github.com/djacobsmeyer/claude-skills-engineering --skill worktree-manager-skill-djacobsmeyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-manager-skill
Source: https://github.com/djacobsmeyer/claude-skills-engineering/tree/main/plugins/manage-worktrees-skill
Command: npx skills add https://github.com/djacobsmeyer/claude-skills-engineering --skill worktree-manager-skill-djacobsmeyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes management of git worktrees for parallel development with isolated ports and configs.

Core Features & Use Cases

Create/Delete/List: Manage full worktree lifecycle
Isolated environments: Unique ports/config per worktree
Quick access: Commands and URLs to monitor and use

Quick Start

Use /create_worktree <branch-name> to create a new isolated worktree.

Frequently Asked Questions about worktree-manager-skill

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

FAQPage Schema

How do I automate git worktree management for parallel development?▼

Automate git worktree management by creating isolated worktrees with unique ports and configurations. Use the /create_worktree command to spin up new branches in parallel, each with its own environment and port allocation, enabling simultaneous development without conflicts.

Can I run multiple git worktrees on different ports simultaneously?▼

Yes, git worktrees run on isolated ports automatically allocated per worktree. Each parallel worktree gets its own port assignment and configuration, allowing multiple services to run concurrently without port collisions or environment interference.

How do I clean up git worktrees and remove isolated environments?▼

Remove worktrees using the deletion command, which automatically handles complete cleanup—tearing down services, freeing allocated ports, and removing per-worktree configurations. The Skill ensures no orphaned processes or stale configurations remain.

What's the quickest way to list and monitor active worktrees?▼

List all active worktrees with quick access to monitoring commands and URLs for each. The Skill provides direct links and command references to track the status and endpoints of every parallel worktree in your setup.

Do I need to manually configure ports and environments for each git worktree?▼

No, port allocation and environment isolation happen automatically per worktree. The Skill propagates configurations and assigns ports without manual intervention, reducing setup overhead and eliminating port conflicts across parallel branches.

Can worktrees share configuration or must each one be isolated?▼

Worktrees maintain isolated configurations by default for parallel independence. Configuration propagation ensures settings flow correctly across worktrees while preserving per-worktree customization and preventing cross-branch interference.