git-worktree

Managing git worktrees for parallel development involves creating isolated directories for each branch. This skill provides a unified manager script to create, list, switch, and clean up worktrees while automatically copying environment files and syncing .gitignore.

The best way to copy environment files when creating a git worktree is using an automated manager script. This skill automatically copies your env files from the main repository into each newly created per-branch worktree directory.

Keeping .gitignore in sync across multiple git worktrees is handled automatically by the manager script. It enforces safe operations and maintains consistent .gitignore management across all active branches within the dedicated .worktrees directory.

Yes, you can safely clean up inactive git worktrees because the manager script enforces safe operations with prompts. It ensures inactive worktrees are removed securely without risking your current parallel development environment.

No, this git worktree workflow does not require external dependencies. It relies on a single internal manager script to handle worktree creation, environment file copying, and branch switching.

You should use git worktrees instead of cloning multiple times when you need isolated parallel development branches sharing a single repository. This approach avoids duplication and simplifies switching between features.