ultraqa

Automate test-build-fix QA cycles until the quality goal is achieved.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Rheinmir/skills-kit --skill ultraqa-rheinmir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/Rheinmir/skills-kit/tree/main/skills/ultraqa
Command: npx skills add https://github.com/Rheinmir/skills-kit --skill ultraqa-rheinmir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UltraQA provides an autonomous QA cycling workflow that runs until your quality goal is met, reducing manual back-and-forth between test, verify, and fix phases.

Core Features & Use Cases

  • Autonomous QA cycling: Continuously runs tests, verifications, and fixes across cycles until success.
  • Cycle-driven workflow: Defines steps (qa-tester → architect verification → fix → repeat) and tracks progress.
  • Stateful execution: Maintains a state file to record active goals, cycles, and failures for audit and recovery.

Quick Start

Start UltraQA by initiating a goal-driven QA cycle and letting the system execute tests, diagnose failures, and apply fixes automatically.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate the test, build, and fix loop for continuous integration?

Autonomous QA cycling automates continuous integration loops by running tests, diagnosing failures, and applying fixes across repeated cycles until success. It tracks metrics per cycle and maintains a state file for audit and recovery.

What is an autonomous QA cycle and how does it work?

An autonomous QA cycle continuously runs tests, diagnoses failures via an architect, applies fixes via an executor, and repeats until a quality goal is achieved. It maintains a persistent state file to track active goals, cycles, and failures.

Can I use autonomous QA cycling for custom checks and lint typechecks?

Yes, autonomous QA cycling supports tests, build, lint, typecheck, and custom checks as defined goal types. You initiate a goal-driven cycle, and the system executes those specific checks, diagnoses failures, and applies fixes automatically.

How do I start a goal-driven QA cycle for my software project?

Start a goal-driven QA cycle by defining a goal type like tests, build, lint, typecheck, or custom. The system then automatically executes testing, architect verification, and fixing steps, using a persistent state file to track cycles and failures.

What are the limitations of autonomous QA cycling for debugging?

Autonomous QA cycling is limited to defined goal types like tests, build, lint, typecheck, or custom checks. It requires a persistent state file to drive repeated cycles and an architect and executor workflow, making it unsuitable for undefined or unstructured debugging scenarios.