git-worktrees
/git-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.
- Author
- helx0071 ↗
- Repository
- skillsmo ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.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
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.
Original author description
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.
How it works
- Goal
- Workflow
- Decision rules
- Boundaries
- Completion standard
- Further reading
SKILL.md preview
--- name: git-worktrees description: "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." --- # Git worktree workflow ## Goal Keep branch and filesystem state explicit while avoiding accidental edits, commits, or cleanup of the wrong worktree. ## Workflow 1. Inspect repository root, branch, status, current worktrees, and the requested task's isolation needs. 2. Choose a unique worktree path and branch name; confirm the target branch exists or the intended starting commit is known. 3. Create the worktree without cleaning or changing the original checkout; verify branch, path, and status. 4. Make and review changes in the isolated path, keeping each worktree's branch and generated files distinct. 5. Before removal, verify the worktree path and branch, preserve or commit needed changes, then remove only the explicitly disposable worktree. ## Decision rules - Use a detached worktree for read-only inspection; use a named branch for changes that need preservation. - Do not reuse a path containing unreviewed user work. - If two worktrees share a branch, pause and understand Git's checkout restriction before proceeding. ## Boundaries - Never reset, clean, prune, or delete worktrees merely to resolve an unfamiliar state. - Never remove the active or only copy of uncommitted user changes. ## Completion standard Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request. ## Further reading - [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases. - [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
- SKILL.md 2 KB
- references/field-guide.md 1 KB
- references/source-notes.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · helx0071/skillsmo | 90 | MIT |
| hellblazer/nexus | 100 | AGPL-3.0 |
| lvlup-sw/exarchos | 100 | Apache-2.0 |
| bostonaholic/rpikit | 100 | MIT |
| workbench-soft/agent-skills | 98 | MIT |
| NeoLabHQ/context-engineering-kit | 91 | GPL-3.0 |
| jagreehal/jagreehal-claude-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 914a206bf37d (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-worktree
Use when work needs an isolated git worktree, such as parallel feature branches, reviewing a PR without disturbing the current checkout, or cleaning up old worktrees. - 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. - 98using-git-worktrees
Use when you need multiple branches checked out at once — create isolated working directories for parallel development without cloning the repository repeatedly - 100git-worktree
Manage git worktrees for isolated parallel development. Use when running multiple sessions concurrently or working on parallel features. - 100git-worktree
Manage Git worktrees for isolated parallel development. Use when creating, switching, or cleaning up worktrees for parallel bead work. - 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…