What problem does it solve?
Development teams using git worktrees for parallel feature branch work frequently encounter port conflicts between concurrent environments, contention for singleton shared resources like Feishu WebSocket channels, test isolation failures caused by shared service state, and excessive manual configuration overhead when switching between branches.
Core Features & Use Cases
- Three-Layer Service Separation: Automatically classifies project services into global shared infrastructure (L1), worktree-exclusive isolated services (L2), and hot-reloaded host processes (L3) to eliminate cross-branch data conflicts.
- Automatic Port Conflict Resolution: Uses deterministic hash-based port offsets to assign unique ports to each worktree, removing the need for manual port configuration when running multiple environments concurrently.
- Exclusive Shared Channel Switching: Implements a safe switching mechanism for singleton channels (e.g., Feishu WS) to ensure only one worktree holds the connection at a time, preventing unexpected disconnections during parallel work.
- Use Case: A 3-person engineering team working on separate feature branches can each run their development environment in their own worktree simultaneously, with no port clashes, no shared service interference, and no manual environment setup.
Quick Start
Use the multi-worktree-dev skill to design a layered parallel development environment for your team's concurrent git worktree workflow, including service isolation rules, port management configuration, and shared channel switching logic.
