worktree-manager-skill

You can manage git worktrees for parallel development by applying automated commands to create, list, and remove isolated environments across multiple branches without manual git worktree commands. This handles port isolation, configuration, and safe cleanup.

Isolating feature development environments is best achieved by creating separate git worktrees for each branch. This allows you to develop features in parallel directories, maintaining isolated configurations and port mappings without constantly switching branches.

To list all active git worktrees, you apply a command that returns existing worktrees alongside their port mappings, statuses, and access URLs. This provides a quick overview to triage parallel environments and identify potential conflicts.

Yes, you can automate worktree cleanup by applying a remove command that safely deletes the worktree. This process stops active services, cleans up directories, and frees allocated ports to prevent conflicts across your parallel development workflow.

No, you do not need manual git commands to set up isolated dev environments for PR testing. The orchestration skill automates the end-to-end lifecycle, including environment creation, port isolation, configuration, and safe removal for automated testing.

You should use git worktrees for parallel branch workflows when you need isolated environments for feature development, PR isolation, hotfix experimentation, or automated testing across multiple branches simultaneously without stashing or switching contexts.