batch-issue-fix

Triage and fix multiple GitHub issues with per-issue plans and optional PRs.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill batch-issue-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: batch-issue-fix
Source: https://github.com/PLeVasseur/opencode-project-agents/tree/main/safety-critical-rust-coding-guidelines/skills/batch-issue-fix
Command: npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill batch-issue-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and fix multiple GitHub issues with a repeatable workflow.

Core Features & Use Cases

  • Batch issue triage: Read, prioritize, and plan fixes for a list of issues in a deterministic order.
  • Per-issue planning: Generate a dedicated plan file for each issue with expected steps and test ideas.
  • Batch execution & reporting: Create a batch plan, execute issue fixes in sequence, and summarize progress with optional PRs.

Quick Start

Provide ISSUE_URLS in the given order to batch-triage and fix issues.

Frequently Asked Questions about batch-issue-fix

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

FAQPage Schema
How do I batch triage and fix multiple GitHub issues automatically?

Batch triage and fix multiple GitHub issues by providing a configurable list of ISSUE_URLS. The workflow reads issues in deterministic order, generates per-issue plan files with steps and test ideas, and executes fixes sequentially with optional PR creation.

What is the best way to plan fixes for a large backlog of GitHub issues?

Planning fixes for a large backlog of GitHub issues involves generating a dedicated plan file for each issue. This batch processing approach creates expected steps and test ideas per issue before executing fixes in sequence and summarizing progress.

Can I create pull requests automatically when batch fixing GitHub issues?

Yes, you can create pull requests automatically when batch fixing GitHub issues. The workflow supports optional PR creation upon request after generating and executing the batch plan across the provided issue URLs.

Do I need any dependencies to batch process GitHub issue queues?

No external dependencies are required to batch process GitHub issue queues. The workflow operates independently to read, prioritize, plan, and fix issues across repositories using only the configurable ISSUE_URLS input.

How does batch issue triage handle execution order across repositories?

Batch issue triage handles execution order deterministically based on the provided ISSUE_URLS sequence. It reads issues in the given order, creates per-issue plans, generates a batch plan file, and executes fixes sequentially for teams managing large queues.

When should I use batch issue fixing instead of handling issues one by one?

Batch issue fixing is suited for teams managing large issue queues across repositories who need a repeatable workflow. It enables parallel issue reads, plan generation, and sequential per-issue execution rather than manual individual handling.