worktree-manager

Managing git worktrees for parallel development involves creating isolated directory branches so you can work on multiple features simultaneously without polluting the main repository. This Skill automates that process using commands like /wt-new and /wt-list to coordinate branches and directories.

Yes, you can run multiple Claude Code instances concurrently by isolating each instance in its own git worktree. This Skill creates separate worktrees with independent memory initialization, allowing side-by-side testing and feature development without conflicts.

The best way to merge worktree changes back to the main branch is using the /wt-merge command, which coordinates controlled merging of isolated branch directories. This ensures parallel feature work integrates cleanly without polluting the main repository.

Yes, you need git installed to automate worktree creation and cleanup. This Skill relies on git's native worktree functionality to execute commands like /wt-new, /wt-list, and /wt-clean for managing parallel development directories and branches.

Worktree cleanup works by using the /wt-clean command to safely remove isolated feature directories after merging is complete. This Skill automates the cleanup process, ensuring stale branches and worktree directories are removed without affecting the main repository.

You should use parallel git worktrees instead of standard feature branches when you need to start several features at once or run different Claude contexts for testing side-by-side. Worktrees keep changes isolated in separate directories, preventing branch switching overhead and main repository pollution.