ultraqa

Automate iterative QA cycles by testing, diagnosing, fixing, and rechecking until success or blocker.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill ultraqa-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/ultraqa
Command: npx skills add https://github.com/akillness/jeo-skills --skill ultraqa-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run an autonomous QA cycling workflow: test, diagnose, fix, and repeat until the quality goal is met or a concrete blocker is proven. Use when the user explicitly invokes $ultraqa, ultraqa, asks for QA cycling, test/build/lint repair, or a parallel review burst. Also tolerate the common typo $ultaqa by treating it as $ultraqa.

Core Features & Use Cases

  • Automated QA cycling: run tests, diagnose failures, apply fixes, and re-verify until success or blocker.
  • Typo-tolerant invocation: accepts common aliases like $ultaqa and routes to the same workflow.
  • Repo-native integration: leverages existing project commands (tests/build/lint/typecheck) and preserves failure evidence for audit.

Quick Start

Begin an ultraqa cycle by invoking the command with your repository's QA goals.

Frequently Asked Questions about ultraqa

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

FAQPage Schema
How do I automate an end-to-end QA cycle for test, build, and lint failures?

Automated QA cycling executes tests, diagnoses failures, applies fixes, and rechecks until success or a concrete blocker. It leverages repo-native verification commands to preserve failure evidence and ensure repository integrity.

What is autonomous QA cycling and when do I need it for code quality?

Autonomous QA cycling is an iterative process that runs tests, diagnoses failures, and applies fixes until quality goals are met. It is needed for repository-wide QA workflows including tests, builds, lint, and typecheck.

How do I run parallel review bursts for repository-wide QA workflows?

Parallel review scenarios are supported by the QA cycling workflow, executing repo-native verification scripts and iterating fixes. It stops automatically when progress stalls or a concrete blocker is proven.

Do I need existing test scripts to run automated QA diagnosis and repair?

Yes, automated QA diagnosis depends on repo-native verification commands and existing scripts. It uses these to verify integrity, diagnose failures, apply fixes, and preserve failure evidence for audit.

What happens when automated QA cycling stalls and cannot fix a test failure?

When progress stalls during QA cycling, the workflow stops and reports a concrete blocker. It preserves failure evidence from the repo-native verification commands for manual diagnosis and audit.

Can I use ultraqa for typecheck and build repair in my repository?

Yes, ultraqa automates QA cycling for tests, builds, lint, and typecheck repair. It executes repo-native commands, diagnoses failures, applies fixes, and rechecks until success or a blocker.