orchestrate-issue

Automate GitHub issue code-to-review-to-PR workflow with mix test verification.

11|Updated Dec 28, 2024
One-click install
npx skills add https://github.com/wadvanced/aurora_uix --skill orchestrate-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate-issue
Source: https://github.com/wadvanced/aurora_uix/tree/main/.claude/skills/orchestrate-issue
Command: npx skills add https://github.com/wadvanced/aurora_uix --skill orchestrate-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate a repeatable coding workflow for a GitHub issue by driving code implementation, structured review, and tests until the work is ready for a PR.

Core Features & Use Cases

  • Enforces an enriched-spec precondition: Verifies the issue body already contains the enriched-spec marker before starting the coding loop.
  • Runs iterative code → review cycles: Alternates code-issue modes and updates the issue’s review-gaps block based on review results.
  • Finalizes with a PR workflow: Runs a final mix test gate, marks completion in the issue body, and invokes pr-from-issue when ready.

Quick Start

Run orchestrate-issue for issue #123 after you have already run improve-issue so the issue body contains the enriched-spec marker block.

Frequently Asked Questions about orchestrate-issue

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

FAQPage Schema
How do I automate a GitHub issue code review loop for Elixir projects?

Automate a GitHub issue code review loop by orchestrating iterative code implementation, structured review gap tracking, and deterministic mix test verification before creating a pull request.

What is the enriched-spec marker required before starting issue orchestration?

The enriched-spec marker is a specific block within the GitHub issue body that must exist to verify the issue is fully specified before the automated coding and review loop can begin.

How do I run iterative code and review cycles for a Phoenix LiveView pull request?

Run iterative cycles by alternating code-issue modes to generate implementation, updating the issue's review-gaps block, and enforcing mix test consistency until the Phoenix LiveView changes are ready.

Can I generate a pull request automatically after mix test passes on a GitHub issue?

Yes, you can generate a pull request automatically by running a final mix test gate, applying an idempotent completion marker to the issue body, and then invoking pr-from-issue.

What prerequisites are needed to orchestrate issue workflows with mix test verification?

Prerequisites include a numeric GitHub issue id, an existing enriched-spec marker block in the issue body, and an Elixir environment capable of running mix test and mix consistency checks.

Why does issue orchestration require updating a review-gaps block during the code cycle?

Updating the review-gaps block is required to track unresolved structural review findings iteratively, ensuring all implementation gaps are closed before final mix test verification and pull request generation.