using-git-worktrees

To create an isolated git worktree, the system uses priority-driven directory discovery to find a location, validates ignore rules, and sets up the worktree with automated environment setup commands for safe feature development.

Git worktree content appears in commits when the worktree directory is not ignored. The system prevents this by verifying safety rules and automatically updating .gitignore to exclude worktree directories from accidental commits.

Using git worktrees is the best way to manage branches without switching context, as it creates isolated workspaces sharing the same repository, keeping feature work separate from the main workspace and protecting mainline stability.

The automated environment setup detects the project name, creates the worktree, and auto-installs dependencies by running project setup commands as needed, followed by a clean baseline check to ensure readiness for feature development.

Yes, you can use a global location for git worktrees. The directory discovery follows a strict priority, checking local directories like .worktrees or worktrees first, then applying optional global paths and preferences via superpowers rules.

A key limitation is ensuring the worktree directory is properly ignored by Git to prevent accidental commits. The system mitigates this by strictly validating ignore rules and updating .gitignore, but users must manage post-workflow cleanup manually.