isolated-worktree-session

An isolated development environment uses a git worktree to create a temporary branch, allowing you to edit code concurrently without affecting your primary branch or interfering with other developers' changes.

A git worktree session sets up a temporary, disjoint workspace within your repository, needed when you develop code in parallel and want to prevent cross-pollution between concurrent work sessions.

No, nested worktree isolation is blocked because the skill detects linked worktrees early, preventing unnecessary environment setup if you are already operating within an isolated worktree.

You must manually clean up the temporary worktree after your session, allowing you to either cherry-pick commits back to your main branch or discard the isolated changes as needed.

Yes, starting an isolated worktree session requires a clean branch to ensure the temporary worktree environment is established from a stable repository state before disjoint code editing begins.

A dedicated worktree session provides explicit code isolation by locking development to a temporary workspace, minimizing conflicts between concurrent sessions and improving code quality beyond a standard branch.