creating-git-worktree

Git worktrees for parallel development are set up by creating isolated working directories linked to a single repository. This skill automates that process by syncing with the default remote branch and generating a dedicated worktree inside a local .git-worktrees directory.

Yes, environment files are automatically copied when creating a new git worktree. This skill detects optional .env and .serena files in your repository and duplicates them into the new worktree directory for immediate use.

The best way to manage git worktree environments during context switching is using an automated script that provisions isolated directories. This skill reuses existing worktrees to avoid duplicates and applies branch-name substitutions to keep your workspaces organized.

Yes, a remote default branch is required to automate git worktree creation. This skill syncs the new worktree with the remote default branch to ensure your isolated environment starts from the correct project state.

To prevent duplicates, the script checks for existing worktrees and reuses them if one already exists for the target branch. This avoids redundant directory creation and preserves your current worktree state across parallel branches.

Automated git worktree scripts require bash, git, grep, awk, and tr to execute properly. These dependencies handle repository synchronization, branch name substitutions, and environment file copying during the worktree setup process.