using-git-worktrees

To create a git worktree, you set up an isolated directory for a new feature branch, allowing you to develop safely without modifying the main workspace. The workflow includes project-name detection, worktree setup, optional dependency installation, and baseline verification.

Managing multiple git branches in parallel is best achieved by using isolated git worktrees. This allows you to run parallel feature development across multiple directories while preserving a clean main branch without needing to stash changes.

Yes, git worktree creation enforces safe directory selection and ignore verification to prevent polluting the main repository. These safety checks ensure you do not accidentally commit worktree contents to your primary branch.

You can use both project-local and global locations for git worktree isolation. The workflow applies safety guards to discover existing worktree directories and reads CLAUDE.md preferences if present to determine the optimal setup location.

Git worktree setup automatically detects package managers to perform optional dependency installation after creating the worktree. It then runs baseline verification to ensure the new feature branch environment is correctly built and ready for development.

You should avoid using git worktrees if your project lacks proper ignore rules, as safe directory selection relies on ignore verification to prevent polluting the repository. Without these safety guards, worktree contents risk accidental commits.