dev-ultraqa

Run build, lint, and tests up to five cycles until green.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-ultraqa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-ultraqa
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-ultraqa
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-ultraqa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates iterative QA cycles by repeatedly running build, lint, and tests with a circuit breaker that stops after the same error recurs three times, preventing endless loops on fundamental issues.

Core Features & Use Cases

  • Cyclic QA: automatically repeats build, lint, tests, and fix steps up to five cycles to green.
  • Smart escalation: stops early on persistent errors and escalates to architectural review.
  • Use Case: teams implementing new features can ensure all checks pass across multiple passes before merge.

Quick Start

Run the dev-ultraqa workflow to cycle through build, lint, and tests up to five times until all checks pass.

Frequently Asked Questions about dev-ultraqa

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

FAQPage Schema
How do I automate running build, lint, and tests until they pass before merge?

Automated QA cycles iterate through build, lint, and test steps up to five times to reach a green state before merge. The workflow automatically applies fixes between cycles until all checks pass.

What happens if automated test cycles keep failing on the same error?

A circuit breaker stops the automated QA cycles when the same error recurs three times, preventing endless loops on fundamental issues and escalating the problem to architecture review.

Can I use automated QA verification for multi-file refactors across teams?

Yes, the iterative QA verification workflow applies to multi-file feature work and refactors across teams, enforcing agent coordination to ensure checks pass before merge.

What is the maximum number of QA cycles allowed when running build and lint checks?

The automated QA process enforces a maximum of five cycles to reach a green state. If persistent issues cannot be fixed within this limit, it escalates to architecture review.

Why does my continuous integration loop endlessly on recurring build errors?

Continuous integration loops endlessly because basic automation lacks a circuit breaker. This iterative QA workflow stops after the same error recurs three times to prevent infinite loops on fundamental issues.