ultraqa

Repeatedly run quality checks and fix failures until goals are met.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UltraQA turns failing test/build/lint/typecheck runs into a repeatable loop that keeps diagnosing and fixing issues until your chosen quality goal is satisfied.

Core Features & Use Cases

  • Goal-driven QA cycling: Runs the right verification command based on flags like tests, build, lint, typecheck, or a custom success pattern.
  • Architect diagnosis to root cause: When a cycle fails, it spawns an architect subagent to analyze output and propose specific fixes.
  • Executor-based patching: Applies recommended changes via an executor subagent, then repeats the cycle.
  • Progress tracking and safe exit: Stops after max cycles or early-stops on repeated failures, and uses a state file to track cycle history.

Quick Start

Activate UltraQA by running /oh-my-claudecode:ultraqa --tests to cycle test runs, diagnose failures, apply fixes, and stop once all tests pass.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate fixing failing test runs until all tests pass?

Automating test fix loops requires a continuous cycle that runs verification commands, diagnoses failures, applies patches, and repeats until success. UltraQA orchestrates this by spawning an architect subagent to diagnose root causes and an executor subagent to apply fixes iteratively.

Can I use QA cycling to fix build, lint, and typecheck failures automatically?

Yes, QA cycling can fix build, lint, and typecheck failures automatically. You activate specific flags for each check, and the loop will diagnose the output, apply executor-based patches, and repeat until the chosen quality goal is met or max cycles are reached.

How does iterative test repair diagnose the root cause of a failing build?

Iterative test repair diagnoses root causes by spawning an architect subagent that analyzes the failing command output and proposes specific fixes. An executor subagent then applies those recommended changes before the cycle repeats the verification run.

What happens if my automated code fix loop keeps failing on the same error?

If an automated code fix loop keeps failing, the cycle will early-stop on repeated failure patterns. It also tracks cycle history using a state file and enforces deterministic exit conditions to prevent infinite loops when environment errors occur or max cycles are reached.

Do I need to set a custom success pattern for CI verification cycling?

You do not need to set a custom pattern for standard CI verification; the cycling supports flags for tests, build, lint, and typecheck. However, you can define a custom output-based success criteria pattern if your workflow requires specialized verification.