parallel-prs

bendrucker's avatarfrom bendrucker

Batch-process multiple issues into draft PRs using parallel worktrees. Use when implementing several related issues simultaneously, creating multiple PRs in parallel, or batch-processing a backlog.

⭐4stars🔀1forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

This Claude skill automates the software development lifecycle by batch-processing multiple issues into draft Pull Requests using parallel Git worktrees. It streamlines developer workflows by handling issue fetching, environment setup, code implementation, and PR creation in a single, parallelized operation, significantly reducing manual overhead for managing backlogs and related tasks.

Use Cases

  • Efficient Backlog Grooming: Automatically convert a batch of up to five low-priority issues or technical debt items into draft PRs to accelerate project maintenance.
  • Parallel Feature Development: Implement multiple related sub-tasks of a large feature simultaneously, utilizing parallel worktrees to maintain clean, isolated environments without context switching.
  • Automated PR Initialization: Streamline the creation of draft PRs across different branches, ensuring consistent issue linking (e.g., 'Closes #123') and initial implementation agents are deployed correctly.
nameparallel-prs
descriptionBatch-process multiple issues into draft PRs using parallel worktrees. Use when implementing several related issues simultaneously, creating multiple PRs in parallel, or batch-processing a backlog.
allowed-toolsBash(git:*), Bash(gh:*), Bash(wt:*)

parallel-prs

Constraints

  • Batch size: 5 issues max (larger batches split automatically)
  • No worktree cleanup: PRs may need iteration after CI feedback
  • Issue linking: Closes #123 in PR body (not commit)

Workflow

  1. Load linear, github, or gitlab skill; fetch issue details
  2. Ask user to clarify ambiguities upfront
  3. Plan agents verify paths/line numbers in parallel
  4. Create worktrees with wt switch --create
  5. Implementation agents commit, push, load pull-request skill, create PR
  6. Monitor CI for failures

See workflow.md and agents.md.