autopilot-batch

Orchestrate parallel processing of autopilot-queued issues in isolated worktrees.

421|49|Updated Jul 3, 2014
One-click install
npx skills add https://github.com/joshukraine/dotfiles --skill autopilot-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autopilot-batch
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/autopilot-batch
Command: npx skills add https://github.com/joshukraine/dotfiles --skill autopilot-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the parallel processing of a batch of autopilot-queued issues by running them in background worktree subagents, each with an Opus gating review on every Sonnet-built PR.

Core Features & Use Cases

  • Parallel Processing: Distributes a batch of issues across multiple background subagents for parallel processing.
  • Sonnet & Opus Integration: Utilizes Sonnet for building PRs and Opus for gating reviews to ensure quality.
  • Merge Authorization: Allows selective authorization of issues to be merged directly, with Opus-built and reviewed PRs.

Quick Start

Run the autopilot-batch skill with the --merge flag to specify issues that should be merged directly.

Frequently Asked Questions about autopilot-batch

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

FAQPage Schema
How do I automate parallel processing of queued issues for continuous integration?

Parallel processing of queued issues is orchestrated by distributing them across multiple isolated background worktree subagents, using Sonnet for PR builds and Opus for gating reviews to ensure quality.

How does Opus gating review work on Sonnet-built pull requests?

Opus gating review automatically evaluates every Sonnet-built pull request within isolated worktrees, ensuring code quality standards are met before authorizing any merges to the target application repository.

How do I authorize specific issues to be merged directly in a parallel batch process?

You authorize direct merges by running the batch process with the --merge flag, which specifies exactly which issues should be merged directly after passing the Opus gating review on their PRs.

Do I need access to the target application repository to spawn subagents for code review?

Yes, you need access to the target application repository and the ability to spawn subagents, as the Skill requires spawning isolated worktree subagents to build and review code within that repository.

What is the best way to handle a batch of autopilot-queued issues without blocking the main branch?

The best way to handle a batch of queued issues without blocking is running them in isolated background worktree subagents, which enables parallel processing where Sonnet builds PRs and Opus performs gating reviews independently.