isolated-development

To isolate risky changes, create dedicated git worktrees for each feature to keep commits, branches, and state independent from your main development tree. This prevents experimental work from contaminating the primary branch.

Setting up a worktree for an issue involves auto-creating a branch from issue context, detecting the project type from repository files, and installing dependencies using language-appropriate commands with lockfile priority for Node, Python, Rust, or Go.

A baseline verification gate runs your test suite before work begins, stopping progression when verification fails. This reduces environment-related surprises by ensuring the sandbox passes initial tests prior to implementing changes.

Use git worktrees for issue workflow when starting risky development, infrastructure modifications, new features, or issue resolution where environment setup and test verification are required to prevent unverified changes from polluting the main branch.

Yes, isolated development supports dependency installation across multiple languages by detecting project types from repository files and executing language-appropriate install commands for Node, Python, Rust, and Go environments.

Your feature branch environment fails because unverified changes or missing dependencies contaminate the state. Using a dedicated worktree sandbox with a baseline verification gate catches these environment-related surprises before work begins.