gh-bulk-issues

Orchestrates parallel headless agent instances to debug and fix multiple GitHub issues simultaneously.

27.6k|2.7k|Updated Aug 6, 2024
One-click install
npx skills add https://github.com/mastra-ai/mastra --skill gh-bulk-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-bulk-issues
Source: https://github.com/mastra-ai/mastra/tree/main/.mastracode/skills/gh-bulk-issues
Command: npx skills add https://github.com/mastra-ai/mastra --skill gh-bulk-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixing many GitHub issues one at a time is slow and serial. This Skill lets you act as a supervisor over parallel headless Mastra Code instances, each working in its own git worktree on a separate issue, while you monitor progress, review output, and ship PRs.

Core Features & Use Cases

  • Parallel issue solving: Spawns one headless mc instance per issue in an isolated git worktree, with builds throttled to two at a time to manage CPU.
  • Supervision and reporting: Maintains per-issue report files, checks every process every 3 minutes, and restarts timed-out instances with continuation prompts.
  • Full PR lifecycle: Reviews diffs, creates PRs with conventional commit titles, handles reviewer comments via /gh-pr-comments, and fixes failing CI via /gh-fix-ci.
  • Use Case: Given issue numbers 1234 5678 9012, the Skill creates three worktrees, runs three agents in parallel, and delivers three reviewed PRs referencing Closes #<NUMBER>.

Quick Start

Run the gh-bulk-issues skill with a space-separated list of GitHub issue numbers, or with no arguments to get issue recommendations based on your contribution history.

Frequently Asked Questions about gh-bulk-issues

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

FAQPage Schema
How do I fix multiple GitHub issues in parallel with AI agents?

Provide a space-separated list of issue numbers, and the Skill creates one git worktree per issue, spawns a headless Mastra Code instance in each, and supervises them until PRs are created. Builds run two at a time while all agent instances run in parallel.

What happens if I run gh-bulk-issues without issue numbers?

It uses the GitHub CLI to list open issues and analyzes your git commit history from the past six months to identify your contribution areas. It then recommends matching issues and asks which ones you want to work on.

What happens when a headless agent instance times out?

The supervisor checks the worktree diff and last output to assess progress. If the instance made progress, it is restarted with a continuation prompt summarizing where it left off, so no work is lost.

Does the skill handle PR review comments and failing CI checks?

Yes. After PRs are created, it spawns instances with /gh-pr-comments to address reviewer feedback, and runs gh pr checks to detect CI failures, spawning /gh-fix-ci instances in the same worktree to fix them.

Why does each GitHub issue need its own git worktree?

Each worktree accumulates context such as commits, diffs, and build artifacts that every subsequent agent instance for that issue benefits from. Creating a second worktree for the same issue would lose that context and risk conflicts.