git-worktree
/git-worktree
Manage git worktrees for isolated parallel development. Use when running multiple sessions concurrently or working on parallel features.
- Author
- v1truv1us ↗
- Repository
- ai-eng-system ↗
- Licence
- MIT
- Last repository change
- 09.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Manage git worktrees for isolated parallel development. Use when running multiple sessions concurrently or working on parallel features.
Original author description
Manage git worktrees for isolated parallel development. Use when running multiple sessions concurrently or working on parallel features.
How it works
- Systematic Approach
- Core Commands
- Naming Conventions
- Integration with ai-eng-system
- Best Practices
- Common Workflows
- Troubleshooting
- Anti-Rationalization Table
SKILL.md preview
--- name: git-worktree description: Manage git worktrees for isolated parallel development. Use when running multiple sessions concurrently or working on parallel features. metadata: category: user-invoked version: 1.0.0 disable-model-invocation: true --- Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more. # Git Worktree Skill ## Systematic Approach ## Core Commands ### Create a Worktree ```bash # Create worktree with new branch git worktree add ../project-feature -b feature/user-auth # Create worktree on existing branch git worktree add ../project-bugfix hotfix/critical-fix # Create worktree at specific commit git worktree add ../project-v1 release/v1.0 ``` ### List Worktrees ```bash git worktree list # Output: # /path/to/repo abc1234 [main] # /path/to/project-feature def5678 [feature/user-auth] # /path/to/project-bugfix ghi9012 [hotfix/critical-fix] ``` ### Remove Worktrees ```bash # Remove worktree (after merging branch) git worktree remove ../project-feature # Force remove if worktree has uncommitted changes git worktree remove --force ../project-feature # Prune stale worktree references git worktree prune ``` ## Naming Conventions Use consistent, descriptive names: ```bash # Good: describes the work git worktree add ../myapp-feature-auth -b feature/auth git worktree add ../myapp-bugfix-login -b hotfix/login-error git worktree add ../myapp-experiment-v2 -b experiment/v2-redesign # Bad: ambiguous names git worktree add ../temp -b stuff git worktree add ../test -b wip ``` ## Integration with ai-eng-system Worktrees enable running multiple Claude sessions in parallel: ```bash # Terminal 1: Feature implementation git worktree add ../project-auth -b feature/auth cd ../project-auth claude # Run /ai-eng/work "implement authentication" # Terminal 2: Bug fix (parallel) git worktree add ../project-bugfix -b hotfix/critical-fix cd ../project-bugfix claude # Run /ai-eng/work "fix login timeout" # Terminal 3: Code review cd ../project claude # Run /ai-eng/review ``` ## Best Practices 1. **Create one worktree per task** — Keep worktrees focused 2. **Name descriptively** — Include project prefix and purpose 3. **Clean up after merge** — Remove worktrees when done 4. **Prune regularly** — Run `git worktree prune` to clean references 5. **Use sibling directories** — Keep worktrees next to main repo, not nested 6. **Don't share worktrees** — Each session gets its own worktree ## Common Workflows ### Feature Development with Review ```bash # 1. Create feature worktree git worktree add ../myapp-feature -b feature/new-api cd ../myapp-feature # 2. Develop the feature # ... make changes, commit ... # 3. Push and create PR git push -u origin feature/new-api gh pr create --title "Add new API" --body "..." # 4. Switch back to main cd ../myapp # 5. Clean up after merge git worktree remove ../myapp-feature git branch -d feature/new-api ``` ### Running Tests in Isolation ```bash # Create worktree for test runs (won't affect main) git worktree add ../myapp-tests -b test/run cd ../myapp-tests [run tests for your project] cd ../myapp git worktree remove ../myapp-tests ``` ## Troubleshooting ### Stale Worktrees ```bash # List all worktrees including stale ones git worktree list --verbose # Prune stale references git worktree prune # Manually remove if prune doesn't work rm -rf ../path-to-stale-worktree git worktree prune ``` ### Worktree Won't Remove ```bash # Force remove with uncommitted changes git worktree remove --force ../project-feature # If still failing, remove manually rm -rf ../project-feature git worktree prune ``` ## Anti-Rationalization Table | Excuse | Counter | |--------|---------| | "I'll just switch branches instead of creating a worktree" | Switching branches loses uncommitted work and breaks running processes. Worktrees enable true parallelism. | | "I don't need to clean up old worktrees" | Stale worktrees clutter the filesystem and confuse branch state. Prune regularly. | | "Naming doesn't matter, I'll remember what it's for" | You won't. Descriptive names prevent confusion when juggling multiple worktrees. | | "I can share this worktree with another session" | Shared worktrees cause git lock conflicts. Each session gets its own worktree. | | "The worktree won't remove, I'll just leave it" | Force remove or manually delete. Stale worktrees cause git warnings and confusion. |
Files in this package (2)
- SKILL.md 5 KB
- evals/evals.json 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · v1truv1us/ai-eng-system | 100 | MIT |
| iliaal/ai-skills | 100 | MIT |
| marcusrbrown/systematic | 100 | MIT |
| davidondrej/skills | 100 | MIT |
| bahayonghang/my-ai-cli-toolkit | 100 | MIT |
| yuri-xyz/skills | 100 | MIT |
| julianobarbosa/claude-code-skills | 100 | MIT |
| NikiforovAll/claude-code-rules | 100 | Apache-2.0 |
| siva01c/claude-plugins | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 36bb83126175 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-worktrees
Git worktree management for parallel agent team development. Triggers: 'create worktree', 'worktree setup', or during /delegate dispatch. Do NOT use for branch creation without delegation context. - 100ctx-worktree
Manage git worktrees for parallel agent development. Use when splitting work across independent task tracks. - 100using-git-worktrees
Creates and removes isolated git worktrees for parallel development. Use when starting feature work needing isolation, working on multiple branches simultaneously, or removing one specific worktree and its branch after its PR merges. NOT for simple branch switching, sweeping… - 90git-worktrees
Create and manage isolated Git worktrees for parallel branches or temporary verification. Use when multiple tasks need separate working directories or when protecting uncommitted work during experiments. - 100worktree-ops
Manages git worktrees for isolated parallel work, with safety checks for uncommitted changes and unpushed commits. Use to work on several branches at once, run parallel sessions, or isolate experiments. - 90git-worktree-manager
Manage parallel development with Git worktrees: creation with port allocation, environment sync, branch isolation, and cleanup. Use when working multiple branches at once, running parallel CI validations, or isolating agent workspaces.