using-git-worktrees

Git worktrees isolate feature development by creating dedicated working directories instead of switching branches, preserving a clean baseline and reducing accidental changes. This skill automates that creation, safety verification, and setup process.

Automatic project setup detects the project name and runs relevant setup commands like npm install or cargo build inside the new git worktree. This ensures the isolated workspace has dependencies installed and is ready for immediate feature development.

Managing git worktree directories uses a priority system: it checks for existing project-local directories like .worktrees or worktrees, then falls back to a global location. This ensures organized isolation across multiple projects.

Safety checks for git worktrees involve verifying .gitignore rules to prevent accidentally committing worktree contents to the repository. This skill enforces these checks automatically before proceeding with dependency installation or test verification.

Running tests before starting feature work in a new git worktree verifies a clean baseline, ensuring the isolated environment functions correctly. This skill automates baseline verification to deliver a ready-to-implement workspace.

Yes, git worktrees support safely exploring changes across branches by maintaining separate directories for each branch. This prevents risky branch switching in your main workspace and keeps your baseline clean during exploration.