How do I install the Using Git Worktrees skill?

Run npx skillmds@latest add mkurman/using-git-worktrees in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Using Git Worktrees safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Git Worktrees?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Git Worktrees free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Git Worktrees?

mkurman (@mkurman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Git Worktrees by mkurman — Agent Skill

Name: Using Git Worktrees
Author: mkurman

File contents

-----|--------| | .worktrees/ exists | Use it (verify ignored) | | worktrees/ exists | Use it (verify ignored) | | Both exist | Use .worktrees/ | | Neither exists | Check CLAUDE.md → Ask user | | Directory not ignored | Add to .gitignore + commit | | Tests fail during baseline | Report failures + ask | | No package.json/Cargo.toml | Skip dependency install |

Common Mistakes

Skipping ignore verification

Problem: Worktree contents get tracked, pollute git status
Fix: Always use git check-ignore before creating project-local worktree

Assuming directory location

Problem: Creates inconsistency, violates project conventions
Fix: Follow priority: existing > CLAUDE.md > ask

Proceeding with failing tests

Problem: Can't distinguish new bugs from pre-existing issues
Fix: Report failures, get explicit permission to proceed

Hardcoding setup commands

Problem: Breaks on projects using different tools
Fix: Auto-detect from project files (package.json, etc.)

Example Workflow

You: I'm using the using-git-worktrees skill to set up an isolated workspace.

[Check .worktrees/ - exists]
[Verify ignored - git check-ignore confirms .worktrees/ is ignored]
[Create worktree: git worktree add .worktrees/auth -b feature/auth]
[Run npm install]
[Run npm test - 47 passing]

Worktree ready at /Users/jesse/myproject/.worktrees/auth
Tests passing (47 tests, 0 failures)
Ready to implement auth feature

Red Flags

Never:

Create worktree without verifying it's ignored (project-local)
Skip baseline test verification
Proceed with failing tests without asking
Assume directory location when ambiguous
Skip CLAUDE.md check

Always:

Follow directory priority: existing > CLAUDE.md > ask
Verify directory is ignored for project-local
Auto-detect and run project setup
Verify clean test baseline

Integration

Called by:

brainstorming (Phase 4) - REQUIRED when design is approved and implementation follows
subagent-driven-development - REQUIRED before executing any tasks
executing-plans - REQUIRED before executing any tasks
Any skill needing isolated workspace

Pairs with:

finishing-a-development-branch - REQUIRED for cleanup after work complete

---name: using-git-worktreesdescription: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification--------|--------|| `.worktrees/` exists | Use it (verify ignored) || `worktrees/` exists | Use it (verify ignored) || Both exist | Use `.worktrees/` || Neither exists | Check CLAUDE.md → Ask user || Directory not ignored | Add to .gitignore + commit || Tests fail during baseline | Report failures + ask || No package.json/Cargo.toml | Skip dependency install |## Common Mistakes### Skipping ignore verification- **Problem:** Worktree contents get tracked, pollute git status- **Fix:** Always use `git check-ignore` before creating project-local worktree### Assuming directory location- **Problem:** Creates inconsistency, violates project conventions- **Fix:** Follow priority: existing > CLAUDE.md > ask### Proceeding with failing tests- **Problem:** Can't distinguish new bugs from pre-existing issues- **Fix:** Report failures, get explicit permission to proceed### Hardcoding setup commands- **Problem:** Breaks on projects using different tools- **Fix:** Auto-detect from project files (package.json, etc.)## Example Workflow```You: I'm using the using-git-worktrees skill to set up an isolated workspace.[Check .worktrees/ - exists][Verify ignored - git check-ignore confirms .worktrees/ is ignored][Create worktree: git worktree add .worktrees/auth -b feature/auth][Run npm install][Run npm test - 47 passing]Worktree ready at /Users/jesse/myproject/.worktrees/authTests passing (47 tests, 0 failures)Ready to implement auth feature```## Red Flags**Never:**- Create worktree without verifying it's ignored (project-local)- Skip baseline test verification- Proceed with failing tests without asking- Assume directory location when ambiguous- Skip CLAUDE.md check**Always:**- Follow directory priority: existing > CLAUDE.md > ask- Verify directory is ignored for project-local- Auto-detect and run project setup- Verify clean test baseline## Integration**Called by:**- **brainstorming** (Phase 4) - REQUIRED when design is approved and implementation follows- **subagent-driven-development** - REQUIRED before executing any tasks- **executing-plans** - REQUIRED before executing any tasks- Any skill needing isolated workspace**Pairs with:**- **finishing-a-development-branch** - REQUIRED for cleanup after work complete

Frequently asked questions

Using Git Worktrees