Skip to content

rohitg00/pro-workflow / skills/parallel-worktrees

parallel-worktrees

Unverified

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.

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 -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

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

ScenarioAction
Tests running (2+ min)Start new feature in worktree
Long buildDebug issue in parallel
Exploring approachesCompare 2-3 simultaneously
Review + new workReviewer in one, dev in other
Waiting on CIStart 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
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
webapp-testinganthropics/skillsToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
browser-testing-with-devtoolsaddyosmani/agent-skillsTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
ci-cd-and-automationaddyosmani/agent-skillsAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.Stars: 118kUpdated Claude CodeCodexVerifiedInstall