using-git-worktrees

Creates isolated git worktree workspaces with detection, setup, and baseline test verification.

Updated May 8, 2026
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill using-git-worktrees-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/using-git-worktrees
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill using-git-worktrees-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting feature work directly in your main checkout risks polluting your current branch and mixing unrelated changes. This Skill ensures every implementation task begins in an isolated workspace, using native worktree tools when available and falling back to manual git worktrees otherwise. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree or a submodule before creating anything, avoiding duplicate or phantom workspaces. - Native Tool Preference with Git Fallback: Uses platform-native worktree tools (e.g., EnterWorktree) first, and only runs git worktree add when no native tool exists, with directory selection and .gitignore safety verification. - Project Setup and Baseline Verification: Auto-detects Node.js, Rust, Python, or Go projects to install dependencies, then runs the test suite to confirm a clean baseline before implementation. - Use Case: Before implementing a new feature branch, activate this Skill to spin up an isolated worktree at .worktrees/feature-x, install dependencies, and confirm all tests pass so later failures are unambiguous. ## Quick Start Set up an isolated git worktree for my new feature branch, install the project dependencies, and verify the test suite passes before I start coding.

Frequently Asked Questions about using-git-worktrees

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an isolated git worktree for feature development?▼

Run `git worktree add <path> -b <branch-name>` to create a linked worktree on a new branch. Prefer placing it in a `.worktrees/` directory at the project root, and verify that directory is listed in .gitignore before creating it.

How do I check if I am already inside a git worktree?▼

Compare `git rev-parse --git-dir` with `git rev-parse --git-common-dir`. If the resolved paths differ, you are in a linked worktree; also run `git rev-parse --show-superproject-working-tree` to rule out being inside a submodule.

Should I use git worktree add or a native worktree tool?▼

Use a native worktree tool (such as EnterWorktree or a /worktree command) whenever one is available, since it manages directory placement, branching, and cleanup. Only fall back to `git worktree add` when no native tool exists.

Why should the worktrees directory be added to .gitignore?▼

An unignored worktree directory risks having the entire worktree contents committed into the repository. Verify with `git check-ignore` before creating the worktree, and commit the .gitignore update first if it is not ignored.

What happens if git worktree add fails with a permission error?▼

A permission error usually means the sandbox blocked worktree creation. In that case, inform the user, continue working in the current directory, and still run dependency setup and baseline tests in place.

Why run baseline tests before starting implementation in a worktree?▼

Running the project test suite first confirms the workspace starts clean, so any later test failures can be attributed to your changes. If baseline tests fail, report the failures and ask whether to proceed or investigate.