Parallel Worktrees Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/rohitg00/pro-workflow --skill parallel-worktreesThe instruction itself
10 sections, as written by the authorParallel 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
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take rohitg00/parallel-worktrees from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.