using-git-worktrees

Creates isolated git worktree workspaces with native tool detection and baseline test verification.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/Base-Analitica/mouse-hub --skill using-git-worktrees-base-analitica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/Base-Analitica/mouse-hub/tree/main/.jcode/skills/using-git-worktrees
Command: npx skills add https://github.com/Base-Analitica/mouse-hub --skill using-git-worktrees-base-analitica

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, detecting existing isolation first and falling back to manual git worktrees only when no native tool exists. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already inside a linked worktree or a submodule before creating anything, avoiding nested or duplicate workspaces. - Native Tool Preference: Uses platform-native worktree tools (e.g., EnterWorktree, /worktree commands) when available, falling back to git worktree add only when necessary. - Safe Directory Handling: Selects .worktrees/ or worktrees/ directories, verifies they are git-ignored, and commits the ignore rule if missing. - Baseline Verification: Auto-detects the project stack (Node, Rust, Python, Go), installs dependencies, and runs tests to confirm a clean starting state. - Use Case: Before implementing a new feature branch, ask the assistant to set up an isolated workspace; it will create the worktree, install dependencies, and report that all baseline tests pass. ## Quick Start Ask the assistant to set up an isolated worktree for your new feature and verify the project tests pass before starting work.

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 a new feature branch?▼

Run `git worktree add <path> -b <branch-name>` from your repository root, then change into the new directory. The Skill automates this by selecting a `.worktrees/` directory, verifying it is git-ignored, and creating the branch in one flow.

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 they differ, you are in a linked worktree. Also run `git rev-parse --show-superproject-working-tree` to rule out being inside a submodule, which produces the same signal.

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

Prefer a native worktree tool (such as EnterWorktree or a /worktree command) whenever one is available, because it manages placement, branching, and cleanup automatically. Manual `git worktree add` is only a fallback and can create state the harness cannot track.

Why must the worktrees directory be in .gitignore?▼

If the worktree directory is not ignored, git will track the entire nested worktree contents and accidentally commit them into the repository. The Skill runs `git check-ignore` first and commits an updated .gitignore before creating anything.

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

A permission error usually means the sandbox blocked worktree creation. The Skill reports the denial, then continues working in the current directory, running dependency setup and baseline tests in place instead.