using-git-worktrees

Creates isolated git worktree workspaces with baseline test verification before feature implementation.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/QT-7274/dotfiles --skill using-git-worktrees-qt-7274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-git-worktrees
Source: https://github.com/QT-7274/dotfiles/tree/main/using-git-worktrees
Command: npx skills add https://github.com/QT-7274/dotfiles --skill using-git-worktrees-qt-7274

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting feature work directly in your current checkout risks polluting your working branch and mixing unrelated changes. This Skill ensures every implementation task begins in an isolated workspace, detecting existing isolation, preferring native worktree tools, and falling back to manual git worktrees only when needed. ## Core Features & Use Cases - Isolation Detection: Checks whether you are already in a linked worktree or a submodule before creating anything, avoiding duplicate or phantom worktrees. - Native Tool Preference with Git Fallback: Uses platform-native worktree tools (e.g., EnterWorktree) when available, otherwise creates worktrees via git worktree add with directory selection and .gitignore safety verification. - Project Setup and Baseline Verification: Auto-detects Node.js, Rust, Python, or Go projects, installs dependencies, and runs the test suite to confirm a clean baseline before work begins. - Use Case: Before implementing a new feature branch, ask the assistant to set up an isolated workspace; it will create a worktree at .worktrees/<branch>, install dependencies, and confirm all tests pass. ## Quick Start Use the using-git-worktrees skill to set up an isolated workspace for my new feature branch and verify the baseline tests pass.

Frequently Asked Questions about using-git-worktrees

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

FAQPage Schema
What happens if baseline tests fail in a new worktree?▼

Failing baseline tests indicate a dirty starting state, making later failures ambiguous. The failures are reported and the user decides whether to proceed or investigate before implementation begins.