parallel-worktrees
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.
- Installs
- 161
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rohitg00/pro-workflow --skill parallel-worktrees- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads parallel-worktrees automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
claude --worktree # or claude -w (auto-creates isolated worktree)
Cursor / Any editor:
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 -wauto-creates and cleans up worktrees- Subagents support
isolation: worktreein agent frontmatter Ctrl+Fkills all background agents (two-press confirmation)Ctrl+Bsends a task to background
Workflow
- Show current worktrees:
git worktree list - Create a worktree for the parallel task.
- Open a new editor/terminal session in the worktree.
- When done, clean up the worktree.
Commands
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
FAQ
What does the parallel-worktrees skill do?
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.
How do I install parallel-worktrees?
Run npx skills add https://github.com/rohitg00/pro-workflow --skill parallel-worktrees in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/parallel-worktrees/ (personal) or .claude/skills/parallel-worktrees/ (project).
Which AI agents can use parallel-worktrees?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is parallel-worktrees safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains parallel-worktrees?
It is published by rohitg00 in rohitg00/pro-workflow. It has 161 recorded installs.
More from rohitg00/pro-workflow
token-efficiency
rohitg00/pro-workflow
Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass coding, task profiles, and read-before-write enforcement. Inspired by drona23/claude-token-efficient.
pro-workflow
rohitg00/pro-workflow
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 8 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
wrap-up
rohitg00/pro-workflow
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
deslop
rohitg00/pro-workflow
Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
learn-rule
rohitg00/pro-workflow
Open the skill to read its SKILL.md instructions.
session-handoff
rohitg00/pro-workflow
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work