Menu
Ensure proper lints and documentation rules, then commit. Orchestrates `gate-fix` and `gate-commit`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement a GitHub issue in aurora_uix, an Elixir/Phoenix low-code UI generation library with Ash and Ecto backends, following an enriched spec produced by improve-issue. Use this skill when the user says "implement the issue", "code this up", "start coding", or provides an enriched spec from improve-issue. Also triggers on "fix the gaps", "address the review findings", or "retry with these requirements" — in those cases the gaps live in the review-gaps marker block of the issue body. Always write tests alongside implementation.
Create a pull request with proper formatting and pre-merge checks
Evaluate an already-enriched GitHub issue and recommend whether to keep it as-is (with a model-tier recommendation), declare it already completed, or split it into smaller children. Use when the user says "evaluate this issue", "is this issue too big", "should we split this", "size this issue", "which model should code this", or before kicking off orchestrate-issue on a heavy spec. Requires improve-issue to have been run first — this skill does NOT enrich specs and does NOT modify code. Read-mostly: the only write is an idempotent issue-evaluation marker block on the issue body.
Run `mix consistency` and fix issues. Mechanical issues are fixed in place; refactor-class issues produce a plan for user approval instead of being attempted.
Enrich and clarify a GitHub issue before any coding begins. Use this skill whenever a user says "work on issue", "implement issue", "fix issue", "start from a GitHub issue", or pastes issue text/URL. Always run this FIRST before code-issue — it produces the structured spec that code-issue consumes. Also trigger when the user says "improve issue description" or "clarify requirements".
Review and score the implementation produced by code-issue against the enriched spec from improve-issue. Use this skill when the user says "review the implementation", "check completeness", "validate coverage", or after code-issue finishes. Runs the project quality gate (mix consistency + mix test), produces a scored report, and writes outstanding gaps into the issue body marker block so code-issue Mode B can pick them up. Always run after code-issue, before deciding the issue is done.
| name | gate |
| description | Ensure proper lints and documentation rules, then commit. Orchestrates `gate-fix` and `gate-commit`. |
Thin orchestrator around two sub-skills:
gate-fix — runs mix consistency and fixes issues. Ends with one of
three statuses on a line by itself: STATUS: CLEAN,
STATUS: PLAN_PENDING, or STATUS: BLOCKED.gate-commit — groups the working tree into conventional commits.
Only invoked when the fixer reports CLEAN.gate-fix skill.STATUS: line.CLEAN → invoke the gate-commit skill. Done.PLAN_PENDING → stop. The fixer's Refactor Plan IS the proposed
coding change. Surface it to the user verbatim and in full (do not
summarize, reorder, or trim) and wait for them to approve or amend it
before any code is written. Do not invoke the committer. Re-running
gate after the user resolves the plan re-enters the fixer cleanly.BLOCKED → stop and report what the fixer left behind. Do not
invoke the committer.gate-commit when the fixer did not return CLEAN.