worktree-manager

Git worktrees can be managed by creating isolated directories for each feature branch, allowing you to work on multiple branches concurrently without disrupting the main repository. This skill automates creating, listing, and removing those worktrees.

To create a Git worktree, use the create workflow with a feature name like 'nutrition'. This automatically sets up a new isolated worktree path and branch, enabling immediate parallel development without manual directory configuration.

Yes, you can safely remove a Git worktree after a PR merge using the remove workflow. It includes uncommitted changes warnings to prevent data loss, ensuring clean cleanup of finished feature branches and their isolated directories.

No external dependencies are required to manage Git worktrees with Bash. This skill relies entirely on standard Bash tooling and Git, manipulating worktrees, paths, and branch naming without needing additional packages.

To list active Git worktrees and check their status, use the list workflow. It displays all active worktrees along with their current branches and statuses, providing a clear overview of your parallel development environment.

Switching between Git worktrees requires manually changing directories to the target worktree path. While it eliminates branch switching within a single directory, you must navigate to the specific isolated worktree folder to resume work on that branch.