ultraqa

Automate iterative QA cycles that test, verify, and fix software until a goal is met.

2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill ultraqa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/chanhee-kang/oh-my-gemini/tree/main/skills/ultraqa
Command: npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill ultraqa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates QA cycling to continuously improve software quality by coordinating test, verification, and fix steps until a goal is met.

Core Features & Use Cases

  • Cycle-based QA: Runs tests, builds, linting, type checks, and custom goals in iterative cycles with automatic diagnosis and fixes.
  • Stateful progress: Tracks cycles, failures, and resolutions to surface actionable insights.
  • Safe cleanup: Purges state data when the goal is achieved or cycles end.

Quick Start

  1. Start UltraQA in your project context.
  2. Invoke with a goal, e.g., /oh-my-gemini:ultraqa --tests
  3. Monitor cycles via logs and state files.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate QA cycling to continuously fix failing tests and builds?

Automate QA cycling by running tests, builds, and linting in iterative cycles with automatic diagnosis and fixes until your goal is met. This stateful workflow tracks progress and resolutions to continuously improve software quality.

What is autonomous QA cycling and how does it handle iterative software verification?

Autonomous QA cycling is a workflow that repeatedly tests, verifies, and fixes software until a stated goal is achieved. It coordinates iterative cycles, surfaces actionable insights from failures, and purges state data upon completion.

Can I run type checks and linting in an automated test cycle until they pass?

Yes, you can run type checks, linting, and custom goals in automated iterative cycles. The workflow applies iterative diagnosis and fixes across multiple cycles until the specified quality goal is achieved.

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

Autonomous QA cycling enforces cycle limits and requires structured state tracking to ensure safe, repeatable engagements. You should monitor logs and state files closely, as the process halts when the cycle limit is reached.

How do I start an automated QA cycle for my project context?

Start the automated QA cycle in your project context, invoke it with a specific goal such as tests or builds, and monitor the iterative cycles via logs and state files until the quality goal is met.