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.
Best use case
parallel-worktrees is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using parallel-worktrees should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/parallel-worktrees/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How parallel-worktrees Compares
| Feature / Agent | parallel-worktrees | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# 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
Related Skills
wrap-up
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.
thoroughness-scoring
Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero — pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.
sprint-status
Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.
smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
session-handoff
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".
safe-mode
Prevent destructive operations using Claude Code hooks. Three modes — cautious (warn on dangerous commands), lockdown (restrict edits to one directory), and clear (remove restrictions). Uses PreToolUse matchers for Bash, Edit, and Write.
replay-learnings
Surface past learnings relevant to the current task before starting work. Searches correction history, recalls past mistakes, and applies prior patterns. Use when starting a task, saying "what do I know about", "previous mistakes", "lessons learned", or "remind me about".
pro-workflow
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 5 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
permission-tuner
Analyze permission denial patterns and generate optimized alwaysAllow and alwaysDeny rules. Use when permission prompts are slowing you down or after sessions with many denials.
orchestrate
Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
mcp-audit
Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.
llm-gate
LLM-powered quality verification using prompt hooks. Validates commit messages, code patterns, and conventions using AI before allowing operations. Use to set up intelligent guardrails.