Receber por email
← Voltar para o catálogo

parallel-worktrees

Crie e gerencie worktrees do Git para sessões de codificação paralelas com tempo de inatividade zero. Use quando estiver bloqueado em testes, builds, quiser trabalhar em múltiplas branches, trocar de contexto ou explorar múltiplas abordagens simultaneamente.

2.3kestrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add rohitg00/pro-workflow

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/parallel-worktrees/svg)](https://www.skillteca.com.br/skills/parallel-worktrees)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

| 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
Compartilhar X LinkedIn