ultraqa

Automate QA cycling with iterative testing, verification, and fixing.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/shaun0927/codex-superskills --skill ultraqa-shaun0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/shaun0927/codex-superskills/tree/main/skills/ultraqa
Command: npx skills add https://github.com/shaun0927/codex-superskills --skill ultraqa-shaun0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the QA cycling workflow to continuously test, verify, and fix software until the defined quality goal is achieved, reducing manual debugging and rework.

Core Features & Use Cases

  • Cyclic QA loop: runs through qa-tester, architect verification, fix, and repeat until criteria are satisfied.
  • Stateful cycles: tracks cycle count, failures, and session state to enable resumable QA sessions.
  • Cancellation & cleanup: supports cancel commands and state cleanup to prevent stale runs.

Quick Start

Begin ULTRAQA cycling now by parsing your goal and starting cycle 1.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate iterative QA testing until quality goals are met?

Automated QA cycling continuously runs tests, verifies architecture, applies fixes, and repeats until your software quality goal is met. This loop reduces manual debugging by tracking cycle count and session state for reproducible results.

What is architecture-driven diagnosis in automated software quality cycles?

Architecture-driven diagnosis analyzes your software structure during QA cycles to identify root causes of failures. It runs within the cyclic loop, applying verification before fixes to ensure iterative testing targets actual defects rather than symptoms.

How do I resume an interrupted QA cycle without losing test state?

Resumable QA sessions track cycle count, failures, and session state throughout the testing loop. If interrupted, you can resume from the last tracked cycle state, and use cancellation commands with state cleanup to prevent stale runs from corrupting results.

Does autonomous QA cycling work for projects requiring multiple fix and re-test iterations?

Autonomous QA cycling is designed for software projects requiring iterative testing, verification, fixing, and re-testing across multiple cycles. It tracks state and applies architecture-driven diagnosis to drive code quality toward your defined success criteria.

When should I use automated QA state cleanup during software testing?

Use state cleanup during automated QA cycling when canceling ongoing runs or preventing stale session data from affecting future cycles. It ensures reproducible testing results by clearing tracked cycle counts and failure states before starting fresh iterations.