using-git-worktrees

To create an isolated git worktree, the skill sets up a separate directory that shares your repository while keeping feature work distinct. It auto-detects the project name and verifies gitignore rules to ensure your main workspace remains safe and unaffected.

Managing multiple git worktrees is handled by supporting both project-local directories like .worktrees and global locations. This approach isolates feature work safely, preserving a clean project baseline while allowing you to switch contexts without stashing changes.

Yes, you need git installed in your environment and an active repository context. The skill requires git to perform safety verification by checking ignore rules before creating a new worktree and reporting readiness.

Checking gitignore rules is required to validate safety before creating a git worktree. This verification ensures your isolated workspace respects existing ignore configurations, preventing unwanted files from polluting the new worktree and preserving project baseline integrity.

Yes, you can use global locations instead of project-local directories like .worktrees. The skill automatically selects preferred local or global locations based on your setup, performing safety checks and ignore verification before creating the worktree.

Git worktrees help maintain a clean project baseline by creating isolated workspaces that share the repository but keep feature changes separate. This prevents uncommitted changes from affecting your main workspace, ensuring a stable baseline.