git-worktrees

Git worktrees allow parallel feature development by creating separate working directories that share repository history. This prevents accidental commits to the main branch while enabling simultaneous experiments and isolated feature implementations.

Git worktrees provide isolated working directories for each branch, allowing you to run parallel experiments without switching branches or risking cross-worktree contamination. Unlike standard branching, worktrees keep your main branch safe from accidental changes during feature development.

Yes, this skill performs automatic safety verification by checking .gitignore for project-local directories, setting up the worktree branch, installing dependencies if needed, and running baseline tests to ensure a safe starting point for isolated feature development.

You need isolated git worktrees when starting a new feature, preparing parallel experiments, or isolating development before implementing from a plan. Worktrees prevent accidental changes to your main branch and enforce project-local ignores to avoid cross-contamination.

The best way to prevent accidental commits is using isolated git worktrees with automatic safety verification. This approach separates your feature branch physically, enforces project-local ignores, and sets up a clean environment with baseline tests before you begin coding.