worktree-manager-skill

Create, list, and remove isolated Git worktrees with automated port allocation.

1.5k|387|Updated Jul 13, 2025
One-click install
npx skills add https://github.com/disler/claude-code-hooks-multi-agent-observability --skill worktree-manager-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-manager-skill
Source: https://github.com/disler/claude-code-hooks-multi-agent-observability/tree/main/.claude/skills/worktree-manager-skill
Command: npx skills add https://github.com/disler/claude-code-hooks-multi-agent-observability --skill worktree-manager-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing multiple Git worktrees for parallel development can be complex, involving manual port allocation, process management, and cleanup. This Skill automates the entire lifecycle of Git worktrees, from creation to removal, ensuring isolated, conflict-free development environments so you can focus on your code.

Core Features & Use Cases

  • Full Lifecycle Management: Create, list, and remove Git worktrees with simple, intuitive commands.
  • Automated Isolation: Ensures unique ports, environment variables, and dependency management for each worktree, preventing conflicts.
  • Troubleshooting & Diagnostics: Provides tools and guidance for diagnosing and resolving common worktree issues quickly.
  • Use Case: You need to quickly switch between a feature branch, a hotfix branch, and a demo environment. Instead of stashing and switching, use this skill to create and manage all three as isolated worktrees, each running its own services without port conflicts.

Quick Start

List all my current git worktrees and their status.

Frequently Asked Questions about worktree-manager-skill

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

FAQPage Schema
How do I manage multiple Git worktrees for parallel development?

Create isolated Git worktrees for each branch with automatic port allocation and environment provisioning. This Skill handles worktree lifecycle management—creation, listing, and removal—ensuring each worktree runs independently without port conflicts or configuration clashes.

Can I run multiple Git branches simultaneously without stashing changes?

Yes. Git worktrees let you check out multiple branches at once in separate directories. This Skill automates the setup so each worktree gets its own ports, .env configuration, dependencies, and background services, eliminating manual switching and state management.

What's the best way to set up isolated development environments for feature and hotfix branches?

Use Git worktrees with automated isolation. This Skill provisions each worktree with unique ports, environment variables, and dependency installations, letting you run a feature branch, hotfix branch, and demo environment concurrently without conflicts.

How do I avoid port conflicts when running multiple development servers?

Git worktrees with auto-allocated ports solve this. This Skill assigns unique ports to each worktree and manages .env and .claude/settings.json per worktree, preventing collisions when multiple services run in parallel.

What happens when I remove a Git worktree—do I have to manually clean up services?

No. This Skill handles comprehensive cleanup during worktree removal, including background service shutdown and temporary file deletion, so you don't leave orphaned processes or port bindings behind.

Do I need special knowledge to diagnose worktree issues?

This Skill provides built-in troubleshooting and diagnostics tools via SlashCommand interface to quickly identify and resolve common worktree problems, reducing manual debugging.