issue-loop

Orchestrate a 10-step GitHub issue development lifecycle with impact analysis and adversarial review.

12|2|Updated Jun 19, 2026

Search Tags:#automation #workflow #github #quality-assurance #code-review #dev-process

Ready to run

npx skills add https://github.com/mori-shin-x/artgraph --skill issue-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-loop
Source: https://github.com/mori-shin-x/artgraph/tree/main/.claude/skills/issue-loop
Command: npx skills add https://github.com/mori-shin-x/artgraph --skill issue-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of consistency and quality in issue resolution by enforcing a structured, 10-step development process that prevents common pitfalls like confirmation bias, silent regressions, and incomplete testing.

Core Features & Use Cases

Shift-Left Impact Analysis: Identifies potential breaking changes and ripple effects before a single line of code is written.
Clean Sub-agent Orchestration: Delegates tasks to isolated sub-agents to ensure objective reviews and independent verification of findings.
Use Case: When assigned a complex GitHub issue, use this Skill to drive the entire lifecycle from initial impact assessment and design to implementation, adversarial review, and final merge.

Quick Start

Invoke the issue-loop skill by providing the GitHub issue number or URL to initiate the full 10-step development process.

Frequently Asked Questions about issue-loop

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

FAQPage Schema

How do I automate the GitHub issue resolution workflow to prevent regressions?▼

Automating the GitHub issue resolution workflow requires a structured development process that enforces impact analysis, independent code review, and systematic testing. This Skill orchestrates a 10-step lifecycle to prevent silent regressions and ensure high-assurance quality control.

What is shift-left impact analysis in software engineering and when do I need it?▼

Shift-left impact analysis identifies potential breaking changes and ripple effects before code implementation begins. You need it for complex software engineering tasks where preventing confirmation bias and ensuring deterministic process execution are critical requirements.

How do I execute an adversarial code review for complex GitHub issues?▼

Executing an adversarial code review requires delegating tasks to isolated sub-agents to ensure objective findings and independent verification. This Skill orchestrates clean sub-agent separation to eliminate confirmation bias during the development lifecycle.

Can I use this automated development process for simple bug fixes?▼

This automated development process is designed for complex software engineering tasks requiring high-assurance quality control. Simple bug fixes do not necessitate the rigorous 10-step lifecycle, as the overhead of impact analysis and sub-agent orchestration outweighs the benefits.

What is the best way to ensure deterministic execution and documentation of design decisions?▼

Ensuring deterministic execution and systematic documentation requires a structured 10-step development lifecycle with independent verification. This Skill enforces rigorous process execution, preventing incomplete testing and capturing design decisions throughout the workflow.

Why does my GitHub issue resolution process suffer from confirmation bias?▼

GitHub issue resolution suffers from confirmation bias when the same context handles implementation and review without independent verification. Delegating adversarial review to isolated sub-agents ensures objective findings and eliminates bias in the quality assurance process.