code-issue

Implement GitHub issue acceptance criteria as Elixir/Phoenix/Ash code with tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a GitHub issue’s enriched acceptance spec into working Elixir/Phoenix/Ash code with the required tests, so gaps from review don’t remain ambiguous or unverified.

Core Features & Use Cases

  • Implements acceptance criteria end-to-end: follows the enriched-spec markers and completes all required behavior.
  • Remediates review gaps safely: focuses only on the items listed in the review-gaps block without redoing already-passing work.
  • Ensures correctness with tests: writes tests alongside implementation in Full mode and produces test-hint breadcrumbs in delegated modes.
  • Works with related issues: fetches linked issues when referenced to avoid missing constraints.

Quick Start

Use the code-issue skill to implement the issue that Improve-Issue described, including all acceptance criteria and any review gaps, while ensuring tests are added alongside the changes.

Frequently Asked Questions about code-issue

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

FAQPage Schema
How do I automate Elixir and Phoenix LiveView code generation from GitHub issues?

Automating Elixir and Phoenix LiveView code generation from GitHub issues involves reading an enriched issue specification via the GitHub CLI and implementing the required CRUD, domain, and LiveView changes with corresponding tests.

How do I implement Ash Framework authorization and transaction requirements from GitHub acceptance criteria?

Implementing Ash Framework authorization and transaction requirements from acceptance criteria involves parsing the issue body for edge-case handling and applying Ash authorization policies and transactions directly in the generated Elixir code.

Can I generate automated tests for Ash Framework and Phoenix LiveView changes directly from a GitHub issue?

Yes, generating automated tests for Ash Framework and Phoenix LiveView changes from a GitHub issue writes tests alongside implementation in Full mode and produces test-hint breadcrumbs in delegated testing modes.

What is the best way to remediate GitHub issue review gaps in an Elixir codebase?

Remediating GitHub issue review gaps in an Elixir codebase involves focusing only on the items listed in the review-gaps block without redoing already-passing work, ensuring targeted code fixes are applied.

Does code-issue work with linked GitHub issues to avoid missing Elixir implementation constraints?

Yes, it fetches linked GitHub issues when referenced to avoid missing constraints, ensuring all related Elixir, Phoenix, and Ash implementation requirements are captured before coding.

How do I format and update GitHub issues after implementing Phoenix LiveView changes?

Formatting and updating GitHub issues after implementing Phoenix LiveView changes involves running mix format and mix consistency, then updating the issue with an auditable implementation summary and completion checkboxes.