worktree-setup

Create parallel git worktrees for specified PRs from sprint documentation.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-setup-duanegoodner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-setup
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/worktree_setup
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill worktree-setup-duanegoodner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git worktrees for the specified PRs so they can be developed in parallel, each in its own isolated working copy.

Core Features & Use Cases

  • Automates creation of multiple worktrees from sprint PR specs, enabling parallel development without interfering with the main branch.
  • Validates preconditions such as non-existent worktrees and non-conflicting local branches, and derives target branches from the sprint document.
  • Use Case: A team needs to prepare three PRs (PR A, PR B, PR C) simultaneously; this skill will set up three separate worktrees named after each PR for concurrent work.

Quick Start

Call the worktree_setup skill with the PR labels to generate corresponding parallel worktrees from the sprint data.

Frequently Asked Questions about worktree-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create git worktrees for multiple PRs at once?

This skill automates git worktree creation for parallel PR development by extracting branch names from active sprint documentation and generating a corresponding isolated worktree per PR. It enables concurrent work across multiple pull requests without branch interference.

What is a git worktree and when do I need it for sprint development?

A git worktree provides an isolated working copy for parallel development. You need worktrees for sprint development when preparing multiple PRs simultaneously, allowing you to develop each PR in parallel without interfering with the main branch.

Do I need a bare repository layout to use parallel worktrees for PR development?

Yes, creating parallel worktrees for PR development requires a bare repository layout with a valid main worktree named main. The skill validates preconditions like non-existent worktrees and non-conflicting local branches before creation.

What's the best way to manage isolated branches for concurrent sprint processing?

The best way to manage isolated branches for concurrent sprint processing is generating parallel worktrees from sprint PR specs. This approach validates preconditions and derives target branches directly from sprint documentation to prevent local branch conflicts.

Why does worktree creation fail with conflicting local branches?

Worktree creation fails with conflicting local branches because the skill enforces strict preconditions requiring non-conflicting local branches and non-existent worktrees. This validation prevents branch-management collisions before creating parallel PR development environments.