git-worktree
Use Git worktrees to isolate parallel coding tasks. Use when setting up a task checkout, working in a shared repo, or managing existing worktrees.
Install
With your agent
Install OMGSkills skill "davidondrej/skills:git-worktree" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/davidondrej/skills /tmp/skills && ln -s /tmp/skills/skills/agent-orchestration/git-worktree ~/.claude/skills/git-worktree
From README
Git Worktrees for Parallel Agents In Cloudroom ($ROOMTHREADID is set) Never run git worktree add yourself. Cloudroom only deletes worktrees it made, so hand-made ones pile up in /code forever. New task: start the thread with New worktree instead. Move this thread to its own worktree: fork it into a Cloudroom-managed worktree. Cloudroom makes the branch and deletes the folder once its last thread is archived (after the worktree retention setting, default 21 days). It branches from main, so uncommitted edits stay behind; commit them first or pass --base-branch . Then tell the user to continue in the new thread and archive this one. Skip the rest of this skill. Start here Detect where you are before editing: Primary checkout → create a task-named worktree, complete the below, and cd into it before editing. Worktree (including one created by Cursor) → proceed with the task. Working model Worktrees have separate working files and branches but share Git history, stashes, config, and refs.
