Git Worktrees
When and how to use isolated git worktrees to run parallel work on a repository without branch conflicts.
This is a real, installable Claude Code skill
(
git-tools:git-worktree).
View source on GitHub →What this skill does
Sets up an isolated git worktree — a second working directory checked out from the same repository — so a task can run on its own branch without touching the branch currently being worked on. No stashing, no risk of one task’s uncommitted changes bleeding into another. For everyday git operations see Git; for the Gitflow branching model see Git Flow.
When to use it
- Fixing a bug while another feature is still in progress and shouldn’t be disturbed
- Running two branches at once (e.g. two agents or two terminal sessions working the same repo)
- Isolated, throwaway experiments that shouldn’t touch the main checkout
- Any situation where two sessions might otherwise edit the same files at the same time
Source
This is a real, installable Claude Code skill. The maintained version — including the exact commands and edge cases it handles — lives in the git-tools plugin of the siva01c/claude-plugins marketplace repository. This page is a summary; the linked SKILL.md is the source of truth.