git-worktree

Git worktrees allow isolated parallel development by creating separate working directories for different branches. This skill provides a unified bash script to create, list, switch, and clean up worktrees, keeping your main repository organized.

Yes, when creating a new Git worktree, the skill automatically copies environment files like .env and .env.local from the main repository to the new worktree directory. This ensures your parallel development branches have the necessary configuration.

The best way to switch between Git worktrees is using a centralized bash manager script. This skill provides a worktree-manager.sh script that handles switching between active worktrees safely without needing to manually change directories.

Yes, the skill requires both bash and git to be installed in your environment. It leverages a dedicated worktree-manager.sh script to enforce consistent worktree management and automatically update your .gitignore file.

To safely clean up completed Git worktrees, use the provided worktree-manager.sh script's cleanup command. This ensures the isolated working directories and their associated branches are removed properly without affecting your main repository.

Using a dedicated bash script for Git worktree automation enforces a unified interface for creation, listing, switching, and cleanup. It automatically handles .gitignore updates and environment file copying, reducing manual errors during parallel development.