using-git-worktrees

To create an isolated git worktree, the Skill selects a valid directory location, verifies the path is ignored to prevent tracked file pollution, and sets up a separate branch workspace that keeps your main checkout clean and stable.

Git worktree safety is verified by checking existing conventions, repository guidance, or asking for confirmation, ensuring project-local worktree paths are properly ignored so your tracked files are never polluted during feature development.

The best way to set up a git worktree is to detect the project type, run setup steps, and verify baseline test readiness before implementation begins, ensuring your isolated workspace is fully prepared for branching experiments.

Yes, you can use git worktrees for debugging and plan execution because they provide workspace isolation, allowing you to start a new feature branch in a separate directory without affecting the stability of your main workspace.

You need a git worktree when starting implementation plans, debugging, or tasks that require workspace separation from the current checkout, ensuring your main workspace remains clean while you work in an isolated environment.

Git worktree setup fails if project-local paths are not ignored because tracked files would be polluted, so the Skill applies safety checks to verify directory selection and ignore safety before creating the worktree.