WO

Sets up git worktrees for parallel feature development and opens them in separate editor sessions.

Install

mkdir -p .claude/skills/worktree-parallel && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12896" && unzip -o skill.zip -d .claude/skills/worktree-parallel && rm skill.zip

Installs to .claude/skills/worktree-parallel

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create and manage a git worktree for parallel feature development, then open the new worktree in the editor (code/Cursor) for a second Codex session. Use when the user asks to work on another feature simultaneously, spin up a parallel workspace, or open a new worktree even if they do not mention worktree explicitly.
317 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • Create a git worktree for parallel development
  • Open the new worktree in the editor
  • Suggest a parallel Codex session
  • Determine a feature slug and branch name
  • Choose a base directory for linked worktrees

How it works

This skill automates the process of creating a git worktree, naming its branch, and opening it in a specified editor, then suggests starting a new Codex session within it.

Inputs & outputs

You give it
User request to work on another feature or spin up a parallel workspace
You get back
A new git worktree, opened in the editor, with a suggestion for a parallel Codex session

When to use worktree-parallel

  • Working on multiple features
  • Creating parallel environments
  • Managing git worktrees

About this skill

Worktree Parallel

Workflow

  1. Confirm the repo root (use current working directory unless the user specifies another repo).
  2. Determine a feature slug and branch name.
    • Default branch pattern: feat/<slug>.
    • If the user already has a branch name, use it.
  3. Choose a base directory for linked worktrees.
    • Default for this repo: ../<project_name>-wt (create it if missing).
  4. Create the worktree.
    • New branch: git worktree add -b feat/<slug> <base>/<slug>
    • Existing branch: git worktree add <base>/<slug> <branch>
  5. Open the worktree in the editor.
    • Use code -n <path> (Cursor supports the code CLI).
    • If code is unavailable, ask for the preferred editor command (e.g., cursor -n, code, or another).
  6. Suggest a parallel Codex session in the new worktree.
    • cd <path> && codex
  7. Confirm with git worktree list if needed.

Safety

  • Do not use --force unless the user explicitly asks.
  • Do not remove existing worktrees unless the user requests cleanup.

Optional Cleanup (only if asked)

  • git worktree remove <path>
  • git branch -d <branch>

When not to use it

  • When the user explicitly asks to use `--force` for worktree operations
  • When the user does not want to create a new worktree
  • When the user wants to remove existing worktrees without explicitly asking

Limitations

  • It does not use `--force` unless explicitly requested by the user
  • It does not remove existing worktrees unless explicitly requested by the user
  • It relies on the `code` CLI for opening the editor, or requires user input for an alternative command

How it compares

This skill simplify the setup of a parallel development environment by automating worktree creation and editor integration, which typically involves multiple manual git and editor commands.

Compared to similar skills

worktree-parallel side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
worktree-parallel (this skill)07moNo flagsBeginner
tmux202moReviewIntermediate
worktree-status16moReviewBeginner
tmux03moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry