fix-issue

Automate GitHub issue resolution with parallel subagent task execution and quality gates.

326|35|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/athola/claude-night-market --skill fix-issue-athola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/athola/claude-night-market/tree/main/plugins/sanctum/skills/fix-issue
Command: npx skills add https://github.com/athola/claude-night-market --skill fix-issue-athola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires superpowers:subagent-driven-development, superpowers:writing-plans, superpowers:test-driven-development, superpowers:requesting-code-review, superpowers:finishing-a-development-branch, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Systematically address GitHub issues by decomposing into tasks, dispatching parallel subagents, and applying quality gates between batches.

Core Features & Use Cases

  • Dynamic issue discovery and planning
  • Parallel subagent execution with inter-batch gates
  • Completion and issue update automation

Quick Start

Kick off a multi-issue fix workflow and observe parallel task dispatch and gating.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I automate fixing multiple GitHub issues in parallel?

Automate GitHub issue resolution by decomposing issues into tasks, dispatching parallel subagents to work simultaneously, and applying quality gates between batches. This approach coordinates execution across related issues, retrieves issue content via GitHub APIs, extracts acceptance criteria, generates structured task plans, and gates completion with code review before finalizing updates.

Can I process a single GitHub issue, multiple issues, or a list of issues with the same workflow?

Yes, the workflow accepts flexible input formats: a single issue number, a full GitHub URL, or space-delimited lists of multiple issues. The system retrieves issue content, discovers dependencies, and dispatches subagents accordingly, adapting to your input scope without configuration changes.

What happens between parallel task batches in a GitHub issue fix workflow?

Quality gates apply between batches: after subagents complete work in parallel, the workflow routes code for review before proceeding to the next batch of dependent tasks. This ensures each batch meets standards before downstream tasks begin, preventing cascading failures and maintaining code quality.

Does this work with GitHub's API and CLI, or do I need additional tools?

The workflow uses GitHub APIs and CLI to retrieve issue content, extract requirements, and automate finalization including issue updates. No additional tools beyond GitHub access are required; the system handles discovery, planning, and dispatch natively.

What's the difference between parallel subagent dispatch and sequential task execution?

Parallel dispatch executes independent tasks simultaneously across multiple subagents to reduce wall-clock time. Sequential execution handles dependent tasks in order after quality gates pass. The workflow combines both: parallel work within batches, gating between batches, then sequential completion of tasks with dependencies.

Can I use this for systematic issue triage across a repository with many related problems?

Yes, the workflow is designed for systematic triage and remediation across related issues. It automates discovery, dependency analysis, task planning, parallel dispatch, and completion. Use it to address multiple interconnected issues methodically rather than ad-hoc fixes.