using-git-worktrees
Create isolated git workspaces for feature development
๋ํ ๋ค์์์ ์ฌ์ฉํ ์ ์์ต๋๋ค: obra,Cycleaddict,davila7,Cygnusfear,Doyajin174,DYAI2025,ZhanlinCui,CodingCossack
Developers struggle with context switching when working on multiple branches. This skill creates isolated git worktrees so you can work on features in parallel without losing your current workspace state.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"using-git-worktrees" ์ฌ์ฉ ์ค์ ๋๋ค. Create a worktree for the new payment feature
์์ ๊ฒฐ๊ณผ:
I'm using the using-git-worktrees skill to set up an isolated workspace.
Worktree ready at /projects/myapp/.worktrees/feature/payments
Tests passing (47 tests, 0 failures)
Ready to implement payment feature
"using-git-worktrees" ์ฌ์ฉ ์ค์ ๋๋ค. Set up a workspace to review the api-v2 branch
์์ ๊ฒฐ๊ณผ:
I'm using the using-git-worktrees skill to set up an isolated workspace.
Detected existing .worktrees directory
Verified directory is git-ignored
Created worktree: git worktree add .worktrees/api-v2 -b api-v2
Installed dependencies: npm install
Baseline tests: 23 passing
Worktree ready at /projects/myapp/.worktrees/api-v2
๋ณด์ ๊ฐ์ฌ
์์ All 43 static findings evaluated as false positives. External commands are standard git and build tools with hardcoded or trusted arguments. Filesystem operations are legitimate directory checks. No command injection vectors, credential exposure, or malicious patterns detected.
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (26)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (14)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Feature Development Isolation
Start work on a new feature branch without losing uncommitted changes or breaking the current workspace state
Code Review Preparation
Create a clean isolated workspace to review and test pull request changes without affecting local development
Bug Fix Reproduction
Isolate bug investigation work in a separate worktree while maintaining stable development environment
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Set up an isolated workspace for the feature/auth-improvements branch using git worktrees
Create a worktree for bugfix/memory-leak in the .worktrees directory and run the project setup
Create an isolated worktree from the pull-request-123 branch so I can review changes without affecting my current work
I need to work on the experimental/caching branch while keeping my current changes intact. Set up a worktree and verify tests pass
๋ชจ๋ฒ ์ฌ๋ก
- Always verify worktree directories are git-ignored before creation to prevent accidental commits
- Run baseline tests immediately after worktree creation to establish a clean starting point
- Follow the directory priority order: existing directory > CLAUDE.md preference > ask user
ํผํ๊ธฐ
- Creating worktrees without verifying git ignore status, causing workspace pollution in version control
- Skipping baseline test verification, making it impossible to distinguish new bugs from pre-existing issues
- Hardcoding directory locations instead of checking existing directories and user preferences first
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What is a git worktree and why use it?
Where are worktrees created?
Do I need to install dependencies in each worktree?
What happens if baseline tests fail?
Can I have multiple worktrees at the same time?
How do I clean up worktrees after finishing?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
sickn33๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/using-git-worktrees์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md