pi-issue-runner

Create isolated pi worktrees and multiplexed sessions from GitHub issues.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/takemo101/pi-issue-runner --skill pi-issue-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-issue-runner
Source: https://github.com/takemo101/pi-issue-runner/tree/main
Command: npx skills add https://github.com/takemo101/pi-issue-runner --skill pi-issue-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Pi Issue Runner automates turning GitHub Issues into isolated pi worktrees and multiplexed terminal sessions, enabling parallel development across multiple issues without interference.

Core Features & Use Cases

  • Create per-issue worktrees automatically from a GitHub Issue
  • Launch independent pi instances inside a terminal multiplexer (tmux or zellij)
  • Support multi-agent workflows and AI-assisted workflow selection for concurrent tasks
  • Automatic cleanup of sessions and worktrees after task completion

Quick Start

Run a command like ./scripts/run.sh 42 to start a new pi instance for Issue #42 in a dedicated worktree and multiplexed session.

Frequently Asked Questions about pi-issue-runner

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

FAQPage Schema
How do I run parallel pi instances from GitHub issues in isolated worktrees?

To run parallel pi instances from GitHub issues, you can automate the orchestration of GitHub issues into isolated git worktrees and multiplexed terminal sessions, enabling concurrent development without interference. A command like ./scripts/run.sh 42 starts a dedicated session for an issue.

Does this automation work with both tmux and zellij for multiplexed sessions?

Yes, the automation works with both tmux and zellij for multiplexed sessions. It launches independent pi instances inside your chosen terminal multiplexer, allowing you to handle multiple issues concurrently across isolated worktrees with support for configurable workflows.

What prerequisites do I need to automate GitHub issues into git worktrees?

To automate GitHub issues into git worktrees, your environment requires Git, the gh command line tool, either tmux or zellij, jq, yq, and a Bash environment. These dependencies support the orchestration of worktrees and terminal multiplexer sessions.

How is session and worktree cleanup handled after parallel development tasks complete?

Automatic cleanup of sessions and worktrees is handled by the system after task completion. This ensures that parallel development across multiple GitHub issues does not leave orphaned git worktrees or lingering terminal multiplexer sessions on your machine.

Can I use AI-assisted routing for multi-agent workflows when processing GitHub issues?

Yes, you can use AI-assisted routing for multi-agent workflows when processing GitHub issues. The automation supports configurable workflows and AI-assisted workflow selection to manage concurrent tasks across isolated pi instances and multiplexed sessions.