parallel-worktrees — Claude Code skill: work on branches simultaneously
parallel-worktrees — a skill for Claude Code that creates isolated git worktrees for parallel coding sessions. While tests or builds run in one window, start a new task in another without waiting or switching context.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat parallel-worktrees does
Parallel worktrees eliminate idle time: instead of waiting for a two-minute test run or lengthy build, open a second editor window on an isolated copy of your project and work on a different branch. Each worktree is a full working directory with its own state, so changes stay isolated.
In Claude Code, the skill automates worktree creation and cleanup via the claude -w flag. It supports background agents with isolation: worktree in agent config, lets you send tasks to the background with Ctrl+B, and manage them with Ctrl+F. For other editors (Cursor, Codex), use standard git worktree add and git worktree remove commands.
Before removing a worktree, check its status: git -C ../project-feat status ensures no uncommitted changes exist. When done, run git worktree prune to clean up stale references.
What it helps with
- start a new feature while the main branch builds
- review code in one worktree while developing in another simultaneously
- explore multiple approaches in parallel and pick the best one
- avoid context switching between long test runs
Example prompts for the agent
- Create a worktree for feature-x and open it in a new window while I keep working on main
- Run tests in the background and set up a worktree for bug fixes
- Show me all active worktrees and suggest cleaning up old ones
How to install parallel-worktrees
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill parallel-worktrees -a claude-code3Manually: put the files in place
~/.claude/skills/parallel-worktrees/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/parallel-worktrees/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill parallel-worktrees -a codex2Manually: put the files in place
.agents/skills/parallel-worktrees/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill parallel-worktrees -a cursor2Manually: put the files in place
.cursor/skills/parallel-worktrees/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/parallel-worktrees2Manually: put the files in place
.github/skills/parallel-worktrees/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill parallel-worktrees -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/parallel-worktreesManually: put the files in place
.devin/skills/parallel-worktrees/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about parallel-worktrees
How do I install parallel-worktrees in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. Next, execute npx skills add rohitg00/pro-workflow --skill parallel-worktrees -a claude-code and check ~/.claude/skills/parallel-worktrees/SKILL.md for further instructions.
What does parallel-worktrees do?
It creates and manages isolated project copies (git worktrees) so you can develop on multiple branches at once. In Claude Code, it automates worktree creation with claude -w and lets you run background agents without changes interfering with each other.
How do I clean up a worktree when done?
Verify all changes are committed: git -C ../project-feat status. Then remove the worktree with git worktree remove ../project-feat and clean stale references: git worktree prune.
Source text
SKILL.md · MIT
--- name: parallel-worktrees description: Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously. user-invocable: true --- # Parallel Worktrees Zero dead time. While one session runs tests, work on something else. ## Trigger Use when waiting on tests, long builds, exploring approaches, or needing to review and develop simultaneously. ## Quick Start **Claude Code:** ```bash claude --worktree # or claude -w (auto-creates isolated worktree) ``` **Cursor / Any editor:** ```bash git worktree add ../project-feat feature-branch # Open the new worktree folder in a second editor window ``` Both approaches create an isolated working copy where changes don't interfere with your main session. ## Claude Code Extras These features are Claude Code-specific (skip if using Cursor): - `claude -w` auto-creates and cleans up worktrees - Subagents support `isolation: worktree` in agent frontmatter - `Ctrl+F` kills all background agents (two-press confirmation) - `Ctrl+B` sends a task to background ## Workflow 1. Show current worktrees: `git worktree list` 2. Create a worktree for the parallel task. 3. Open a new editor/terminal session in the worktree. 4. When done, clean up the worktree. ## Commands ```bash git worktree list git worktree add ../project-feat feature-branch git worktree add ../project-fix bugfix-branch git worktree add ../project-exp -b experiment git worktree remove ../project-feat git worktree prune ``` ## Usage Pattern ``` Terminal 1: ~/project → Main work Terminal 2: ~/project-feat → Feature development Terminal 3: ~/project-fix → Bug fixes ``` Each worktree runs its own AI session independently. ## When to Parallelize | Scenario | Action | |----------|--------| | Tests running (2+ min) | Start new feature in worktree | | Long build | Debug issue in parallel | | Exploring approaches | Compare 2-3 simultaneously | | Review + new work | Reviewer in one, dev in other | | Waiting on CI | Start next task in worktree | ## Guardrails - Each worktree is a full working copy — changes are isolated. - Before removing a worktree, verify changes are committed: `git -C ../project-feat status` - Don't forget to clean up worktrees when done (`git worktree prune`). - Avoid editing the same files in multiple worktrees simultaneously. ## Output - Current worktree list - Created worktree path and branch - Instructions for opening a new session
© Rohit Ghumare · MIT · rohitg00/pro-workflow