pi-swarm

Coordinate parallel GitHub issue and PR processing across isolated git worktrees.

11|1|Updated Jan 4, 2026

Search Tags:#automation #worktrees #github #epics #parallel #reviews #orchestrate

Ready to run

npx skills add https://github.com/lsj5031/PiSwarm --skill pi-swarm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pi-swarm
Source: https://github.com/lsj5031/PiSwarm/tree/main
Command: npx skills add https://github.com/lsj5031/PiSwarm --skill pi-swarm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, pi, git, md5sum, and includes scripts (resource) components.

What problem does it solve?

pi-swarm orchestrates the coordination of multiple autonomous agents to handle GitHub issues and PRs in parallel, reducing manual overhead and improving throughput.

Core Features & Use Cases

Parallel issue processing: spawn multiple Pi agents to work on issues and PRs simultaneously across isolated worktrees.
Epic & project orchestration: manage waves of tasks, dependencies, retries, and automated PR creation for large initiatives.
Headless monitoring & resilience: supports resume, heartbeat liveness, and automatic backoff on transient failures for long-running workflows.

Quick Start

Launch a captain workflow for an epic and monitor the .worktrees logs to track progress.

Frequently Asked Questions about pi-swarm

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

FAQPage Schema

How do I process GitHub issues and PRs in parallel using git worktrees?▼

To process GitHub issues and PRs in parallel, pi-swarm orchestrates multiple Pi agents across isolated git worktrees. It coordinates dependency-aware waves and optional PR creation to enable bulk operations without manual overhead.

What is dependency-aware orchestration for parallel GitHub issue waves?▼

Dependency-aware orchestration for GitHub issue waves coordinates task execution based on prerequisite relationships. pi-swarm enforces these dependencies, retry backoff, and state persistence to scale autonomous workflows across isolated worktrees.

Do I need the Pi agent and GitHub CLI installed to orchestrate parallel worktrees?▼

Yes, orchestrating parallel worktrees requires the Pi agent and GitHub CLI installed. pi-swarm depends on gh, jq, pi, git, and md5sum to manage issues, PR reviews, and epic planning across isolated environments.

Can I resume parallel GitHub PR processing if a transient failure occurs?▼

Yes, you can resume parallel GitHub PR processing after transient failures. pi-swarm provides headless monitoring with heartbeat liveness, automatic backoff, and state persistence to recover long-running workflows.

What's the best way to manage epic and project planning across multiple isolated git worktrees?▼

The best way to manage epic planning across isolated git worktrees is using a captain workflow. pi-swarm orchestrates task waves, dependencies, retries, and automated PR creation for large initiatives while tracking progress in logs.