handle-issues

Orchestrate batch GitHub issue processing with gh CLI and batch-orchestrator.sh.

125|16|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/aaddrick/claude-pipeline --skill handle-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handle-issues
Source: https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/handle-issues
Command: npx skills add https://github.com/aaddrick/claude-pipeline --skill handle-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines batch processing of GitHub issues by orchestrating a batch run, handling rate limits, and resuming progress after interruptions.

Core Features & Use Cases

  • Batch issue gathering: Collects issues based on filters and kicks off a batch orchestration run.
  • Agent-based routing: Assigns appropriate frontend or backend agents for each issue type to ensure quality work.
  • Progress tracking & resume: Monitors status.json and supports resuming incomplete batches after interruptions.
  • Automated orchestration: Launches batch-orchestrator.sh to process issues autonomously and report back results.
  • Audit-friendly: Logs per-issue steps and provides a final summary with PR statuses.

Quick Start

  1. Provide a context query to describe the issues to process.
  2. Confirm the scope and base branch; Claude will launch the orchestrator and monitor progress.
  3. Review the final summary and logs after completion.

Frequently Asked Questions about handle-issues

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

FAQPage Schema
How do I automate batch processing of GitHub issues end-to-end?

GitHub issue batch processing is automated by orchestrating issue gathering, agent assignment, and progress tracking via a batch script. The workflow integrates gh CLI and jq to drive an autonomous issue-to-PR pipeline across multiple issues.

Can I resume an incomplete GitHub issue orchestration run after an interruption?

Resuming incomplete GitHub issue orchestration runs is supported by monitoring a status.json file. The batch orchestrator tracks progress continuously, allowing interrupted sessions to resume from the last completed issue without restarting the entire batch.

How does agent-based routing work for GitHub issue resolution?

Agent-based routing assigns appropriate frontend or backend agents to each GitHub issue type to ensure quality work. The orchestrator evaluates issue characteristics and dispatches the matching agent to handle the specific development tasks required.

Do I need gh CLI and jq installed to run GitHub issue automation workflows?

gh CLI and jq are required dependencies for running these GitHub issue automation workflows. The orchestrator script leverages gh CLI for repository interactions and jq for parsing JSON data to drive end-to-end batch processing.

What is the best way to handle GitHub API rate limits during batch issue processing?

Handling GitHub API rate limits during batch issue processing is managed natively by the orchestrator's built-in monitoring. The workflow applies rate-limit handling and session resumption techniques to process large issue batches without hitting API constraints.

How do I monitor PR status and audit logs for automated GitHub issue runs?

Monitoring PR status and audit logs is handled by the orchestrator's built-in progress tracking. The system logs per-issue steps throughout the run and generates a final summary with PR statuses upon batch completion for review.