worktree-manager

To isolate uncommitted changes into a git worktree, the skill proactively detects your WIP state and uses the /wt new command to stash, move, and apply those changes into a separate worktree.

You can manage multiple parallel git worktrees using a dashboard-style overview that displays active worktrees, recovers context like last commits and modified files, and provides automated cleanup recommendations.

To avoid merge conflicts across active worktrees, the skill provides an early warning system that detects potential conflicts proactively and helps coordinate multiple concurrent tasks to minimize them.

You should use git worktrees for parallel development when your repository has uncommitted changes, stashes, or unpushed commits, and you need to keep main branches clean before starting a new implementation task.

You can batch create git worktrees from a list of tasks using the multi-worktree creation feature, which sets up isolated environments for each task and generates automated cleanup recommendations when the work is done.