git-worktrees

Create isolated git worktrees for feature branches with safety checks.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/tesseract-ripple/claude-research-config --skill git-worktrees-tesseract-ripple
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktrees
Source: https://github.com/tesseract-ripple/claude-research-config/tree/main/skills/git-worktrees
Command: npx skills add https://github.com/tesseract-ripple/claude-research-config --skill git-worktrees-tesseract-ripple

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting feature work without isolation risks contaminating the main workspace. This skill creates isolated git worktrees with smart directory selection and safety verification to keep development branches separate and reproducible.

Core Features & Use Cases

  • Priority-based directory selection for worktrees (prefer hidden .worktrees, then worktrees, then user prompts).
  • Safety verification including .gitignore checks for project-local worktrees and explicit guidance when using a global location.
  • Automatic setup: switch into the new worktree, initialize or build as needed, and validate a clean baseline before implementing features.
  • Use Case: a developer can start feature work on a new branch without modifying the main repository state, enabling parallel workstreams.

Quick Start

Ask me to create a new isolated git worktree for your feature branch to keep the main workspace clean.

Frequently Asked Questions about 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?

To create an isolated git worktree, the workspace is separated by running git worktree add for your feature branch, using priority-based directory selection that prefers hidden .worktrees folders to keep the main repository clean.

Why should I use git worktrees instead of switching branches in my main workspace?

Git worktrees prevent contaminating your main workspace by providing a safe, isolated directory for feature work, enabling parallel workstreams without modifying the current repository state or risking uncommitted changes.

How does git worktree setup handle .gitignore safety checks for project-local directories?

Git worktree setup performs safety verification by checking .gitignore rules for project-local directories, ensuring the new worktree location is properly ignored and does not contaminate the main repository tracking.

Can I use a global directory location instead of a project-local git worktree?

Yes, you can use a global directory location for git worktrees, which triggers explicit guidance and safety checks to ensure the isolated workspace remains separate from your main project repository.

What is the best way to start feature work across multiple projects without contaminating the workspace?

The best way to start feature work across projects is using an isolated git worktree, which automatically detects directory preferences or CLAUDE.md hints and validates a clean baseline before implementing features.

Do I need to manually initialize the environment after creating a git worktree?

No, manual initialization is unnecessary because the git worktree setup automatically switches into the new directory, initializes or builds as needed, and validates a clean baseline before you begin feature work.