ultraqa

Run verification commands and fix failures until quality goals pass.

Updated May 20, 2026
One-click install
npx skills add https://github.com/xdkp/oh-my-claudecode --skill ultraqa-xdkp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/xdkp/oh-my-claudecode/tree/main/skills/ultraqa
Command: npx skills add https://github.com/xdkp/oh-my-claudecode --skill ultraqa-xdkp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultraqa eliminates the frustration of repeatedly running tests, interpreting failures, and manually hunting down fixes by coordinating an end-to-end QA loop until your quality goal is satisfied.

Core Features & Use Cases

  • Goal-driven QA cycling: Runs the appropriate verification command (tests, build, lint, typecheck, custom pattern) and keeps cycling until the goal passes.
  • Autonomous diagnosis and repair: Uses an architect subagent to identify root causes and an executor subagent to apply precise fixes.
  • Failure tracking with guardrails: Detects repeated failures across cycles and stops early with a focused diagnosis to prevent wasted iteration.

Use case: You ship a change to a TypeScript repo and need confidence that tests, linting, and type checking all pass; Ultraqa iterates through failing suites, diagnoses the root cause, applies fixes, and repeats until the checks succeed.

Quick Start

Run /oh-my-claudecode:ultraqa with the appropriate flag (for example, --tests) to start a QA cycle and iterate until the verification goal is met.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate running TypeScript tests, lint, and type checks until they pass?

You can automate TypeScript verification cycling by repeatedly executing your project's build, lint, typecheck, or test commands and applying iterative fixes until the defined quality goal succeeds.

What is autonomous QA cycling and how does it diagnose test failures?

Autonomous QA cycling runs verification commands iteratively; on failure, it spawns an architect subagent to identify root causes and an executor subagent to apply precise fixes, tracking state across up to five cycles until checks pass.

How do I set up an auto-fix workflow for continuous integration checks?

To set up an auto-fix workflow, run the QA cycle with the appropriate flag for your verification goal, such as tests or lint. The system will iterate, diagnose failures using subagents, and apply fixes up to a maximum of five cycles.

Can I use this automated diagnosis and repair tool for custom output pattern verification?

Yes, automated diagnosis and repair applies to custom output-pattern verification alongside standard tests, builds, lint, and type checking, iterating through failures and applying fixes until your defined quality goal passes.

What happens when automated test fixing repeatedly fails across multiple cycles?

When automated test fixing detects repeated failures across cycles, it stops early with a focused diagnosis to prevent wasted iteration, as the system tracks failure state and applies guardrails against infinite loops.

What are the limitations of automated QA cycles for workflow orchestration?

Automated QA cycles limit iteration to a maximum of five cycles per run, spawn architect and executor subagents only on failures, and require parsing goal arguments to execute the corresponding verification commands.