Verified:GitHub

worktrees:peer

Create isolated Git worktrees for parallel Claude instances coordinated via pull requests.

4|1|Updated Jan 23, 2026

Search Tags:#git workflow #feature development #worktree #autonomous development #PR #code collaboration #multi-instance

Ready to run

npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-peer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktrees:peer
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/worktrees/skills/peer
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-peer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables autonomous multi-instance development workflows where independent Claude worktrees coordinate via PR-based integration to main.

Core Features & Use Cases

Independent worktrees: Each instance maintains its own worktree and feature scope without cross-branch interference.
PR-based integration: All changes are merged through pull requests to main, ensuring controlled integration.
Conflict avoidance and traceability: Clear area ownership and PR-based reviews minimize conflicts and improve traceability.

Quick Start

Use the worktrees:peer skill to initialize a new autonomous instance:

Create a new worktree: git worktree add -b feature/<id>-<feature> .worktrees/<id> main
Describe the feature and optional --id in your PR description to enable reproducible context.

Frequently Asked Questions about worktrees:peer

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

FAQPage Schema

How do I run parallel git worktrees for autonomous feature development?▼

You can run parallel git worktrees by creating a new branch with `git worktree add` for each instance, allowing independent feature development that publishes changes to main via pull requests.

What is the Explore-Plan-Code-Commit workflow for multi-instance git development?▼

The Explore-Plan-Code-Commit workflow is a structured process for autonomous worktrees where each instance independently explores the codebase, plans changes, writes code, and commits to an isolated feature branch before opening a pull request.

How do I avoid merge conflicts when using multiple git worktrees simultaneously?▼

To avoid merge conflicts with multiple worktrees, maintain clear area ownership for each instance so development streams remain isolated, then integrate all changes through pull request reviews to ensure controlled and traceable merges to main.

Can I use PR-based integration for isolated feature branches without direct commits to main?▼

Yes, PR-based integration ensures all changes from isolated worktrees are merged to main through pull requests, providing controlled integration, conflict avoidance, and traceability for autonomous multi-instance development streams.

How do I initialize an autonomous worktree for a specific feature in git?▼

Initialize an autonomous worktree by running `git worktree add -b feature/<id>-<feature> .worktrees/<id> main`, then describe the feature and optional `--id` in your PR description to enable reproducible context for the instance.