git-worktree

Git worktree creates independent working directories for separate branches, allowing multiple instances to develop features simultaneously. This Skill coordinates branch creation, enforces naming conventions, and establishes symlinks to share configuration across all worktrees.

Yes, you can share settings.local.json across Git worktrees by creating absolute-path symlinks to the main repository. This ensures MCP, command, and skill permissions remain consistent across every parallel development instance.

Managing multiple Claude Code instances is best handled through Git worktree parallel development. This approach isolates each feature branch in its own working directory while enforcing branch naming conventions and sharing configuration via symlinks.

Git worktree branch management requires mandatory symbolic links to settings.local.json in the main repository. This configuration step guarantees that shared MCP and command permissions propagate correctly to all worktrees.

Absolute-path symlinks are needed for Git worktrees because they securely link settings.local.json from the main repository to each worktree. This maintains shared permissions and prevents configuration drift across parallel branches.

You should avoid Git worktree if your workflow does not require running multiple Claude Code instances simultaneously. Without the need for isolated parallel branch development and shared settings via symlinks, standard branch switching is sufficient.