# Using Git Worktrees

> Use when starting feature work that should be isolated from the current checkout, especially in git repositories where a separate worktree would reduce risk.

- Skill: `6bnbn/using-git-worktrees` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 6bnbn/using-git-worktrees`
- Raw SKILL.md: https://api.skillmd.com/api/skills/6bnbn/using-git-worktrees/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 6bnbn (https://skillmd.com/u/6bnbn)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/6bnbn/using-git-worktrees

---

# Using Git Worktrees

## Goal
Create an isolated workspace for risky or long-running changes without disturbing the current checkout.

## When To Use
- large feature work
- risky refactors
- parallel efforts on different branches
- keeping the current workspace stable while another branch is explored

## Rules
- Only use this in git repositories.
- Confirm the target location before creating a new worktree if project conventions are unclear.
- Make sure the worktree path will not be accidentally committed.
- After creating the worktree, run the project's normal setup before making claims about readiness.