Skip to content
Automation
Skill

/dev-ultraqa

QA cycling workflow — repeat build/lint/test/fix cycles up to 5 times until all checks pass. Stops early if the same error repeats 3 times (signals a fundamental issue, not a fixable one).

From plugin
evo-nexus
520193 skills38 agents40 commands9 MCP
Install
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-ultraqa --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/dev-ultraqa

Context preview

The summary Claude sees to decide when to auto-load this skill.

QA cycling workflow — repeat build/lint/test/fix cycles up to 5 times until all checks pass. Stops early if the same error repeats 3 times (signals a fundamental issue, not a fixable one).

SKILL.md

dev-ultraqa.SKILL.md
name: dev-ultraqa
description: QA cycling workflow — repeat build/lint/test/fix cycles up to 5 times until all checks pass. Stops early if the same error repeats 3 times (signals a fundamental issue, not a fixable one).

Dev UltraQA

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

QA cycling: keep running build/lint/test/fix loops until all checks pass — but with a circuit breaker. If the same error persists across 3 cycles, stop and report: it's a fundamental issue, not a fixable one.

Use When

  • After a multi-file implementation (post-`dev-autopilot` or `@bolt-executor`)
  • Pre-merge gate when you want all checks green before review
  • Refactor that touches enough files to risk regressions

Do Not Use When

  • Single-file change → just run `dev-verify` once
  • The first failure is structural → escalate to `@apex-architect`, don't loop

Workflow

Each cycle:

1. Run **build** (`npm run build`, `cargo build`, `go build`) 2. Run **lint** (`npm run lint`, `cargo clippy`, `golangci-lint`) 3. Run **tests** (`npm test`, `cargo test`, `pytest`) 4. **If green:** done, exit cycle, hand off to `@oath-verifier` for final verification 5. **If red:** delegate to `@bolt-executor` or `@hawk-debugger` to fix the failure 6. **Loop** back to step 1

Circuit breaker (3-failure rule)

If the same error fingerprint (file:line + error message) appears in 3 consecutive cycles:

  • STOP the loop
  • Hand off to `@apex-architect` with full context dump
  • The issue is no longer "fix the bug" — it's "question the architecture"

Max iterations

  • Default: 5 cycles
  • After 5 cycles even with different errors: stop and report

Output

Saved to `workspace/development/verifications/[C]ultraqa-{component}-{date}.md`:

## UltraQA Report

### Cycles
1. Build ❌ → fixed by @bolt-executor
2. Build ✅ Lint ❌ → fixed by @bolt-executor
3. Build ✅ Lint ✅ Tests ❌ → fixed by @hawk-debugger
4. ✅ All green

### Final State
- Build: ✅
- Lint: ✅
- Tests: ✅ N passed, 0 failed

### Handoff
- → @oath-verifier for evidence-based verification

Pairs With

  • `@bolt-executor` (fixes during cycles)
  • `@hawk-debugger` (fixes when bugs are non-trivial)
  • `@oath-verifier` (final verification post-cycle)
  • `@apex-architect` (escalation when 3-failure breaker trips)
Read more
Ships withevo-nexus

The open source operating system for AI-powered businesses

Get the whole plugin

Other skills on evo-nexus.