ultraqa

Automate QA cycling with tests, lint, build, and typecheck scenarios.

16|3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sehoon787/my-claude --skill ultraqa-sehoon787
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraqa
Source: https://github.com/sehoon787/my-claude/tree/main/skills/omc/ultraqa
Command: npx skills add https://github.com/sehoon787/my-claude --skill ultraqa-sehoon787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the repeated QA cycle of testing, verifying results, diagnosing failures, and applying fixes until the defined quality goal is achieved, reducing manual toil and speeding feedback.

Core Features & Use Cases

  • Automated QA cycles orchestrate tests, verifications, and fixes across a project to reach a quality goal.
  • Architectural verification & diagnostics identify root causes and guide actionable fixes, cycling until success.
  • Stateful workflow tracks cycles, outcomes, and retries, enabling early exits on persistent failures and clear progress visibility.

Quick Start

Begin ULTRAQA cycling by parsing the 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 QA cycles to continuously test and fix software?

Automating QA cycles involves orchestrating tests, verifying results, diagnosing failures, and applying fixes repeatedly until your quality goal is achieved. This stateful workflow tracks cycles and outcomes under .omc/ultraqa-state.json to manage progress and enable early exits on persistent failures.

What is architecture verification in automated testing workflows?

Architecture verification in automated testing identifies root causes of failures and guides actionable fixes. It works by cycling through diagnostics and verifications across your project until the software successfully meets the defined quality goal.

Can I run parallel tasks for lint, build, and typecheck scenarios during QA automation?

Yes, you can run optional parallel tasks across tests, lint, build, and typecheck scenarios. The automated QA workflow supports multi-cycle execution to continuously verify these scenarios until the quality goal is met.

Do I need a defined goal type to start automated QA cycling?

Yes, a defined goal type is required to start automated QA cycling. You must also have access to project commands for testing and verification, allowing the stateful workflow to parse the goal and begin cycle 1 under .omc/ultraqa-state.json.

Why does my automated QA workflow exit early before reaching the quality goal?

Automated QA workflows exit early when persistent failures are detected across multiple cycles. The stateful tracking mechanism monitors retries and outcomes, triggering an early exit to prevent infinite loops when fixes continuously fail to resolve the diagnosed issues.