ultraqa

Automate iterative QA loops with failure diagnosis and fix application.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/nichobbs/lyric-lang --skill ultraqa-nichobbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/nichobbs/lyric-lang/tree/main/.claude/skills/ultraqa
Command: npx skills add https://github.com/nichobbs/lyric-lang --skill ultraqa-nichobbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the burden of repeatedly running QA checks, diagnosing failures, applying fixes, and re-running until your testing or quality goal is satisfied.

Core Features & Use Cases

  • Goal-driven QA cycling: Runs the right verification loop for --tests, --build, --lint, --typecheck, or --custom output pattern matching.
  • Failure diagnosis and fix iteration: Escalates to an architect for root-cause analysis and then an executor to apply targeted fixes.
  • Stateful observability and safe early exits: Tracks cycles and failures, supports cancellation, and stops when goals are met, the max cycle count is reached, the same failure repeats three times, or an environment error occurs.

Example use case: You need all CI checks to pass before merging, so you run UltraQA to test, diagnose failing suites, apply recommended code changes, and keep cycling until everything is green.

Quick Start

Start a 5-cycle QA cycle by invoking ultraqa with the tests goal for your repository.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate QA workflows to run tests, diagnose failures, and apply fixes until they pass?

Automated QA workflows cycle through running verification commands, diagnosing failures, and applying targeted fixes iteratively until your testing goal is met or a maximum of five cycles is reached.

What is iterative QA cycling and how does it handle repeated build or test failures?

Iterative QA cycling repeatedly runs verification commands and applies fixes. It tracks state in a JSON file and safely exits early if the same failure repeats three times or an environment error occurs.

How do I set up automated state tracking for CI verification loops?

Automated state tracking for CI verification loops records cycle counts and failure statuses in a structured JSON file, ensuring deterministic cycle control and supporting safe cancellation during execution.

Can I run custom success-pattern checks alongside lint and typecheck verification?

Yes, custom success-pattern checks run alongside lint, typecheck, build, and test execution. The system parses your goal from command arguments to determine the correct verification loop to apply.

What is the best way to autonomously fix failing CI checks before merging code?

To autonomously fix failing CI checks, use a goal-driven QA process that escalates failures to an architect for root-cause analysis, then an executor applies fixes until all checks are green.

What are the limitations of autonomous QA cycling for software projects?

Limitations of autonomous QA cycling include a strict maximum of five iteration cycles and guarded early-exit behavior that halts the process if the same failure repeats three times or an environment error occurs.