Agent Skills › evolution-foundation/evo-nexus › dev-ultraqa

dev-ultraqa

GitHub

执行构建、Lint和测试的自动化循环修复流程，最多5轮。若相同错误连续出现3次则触发熔断机制并升级架构问题。适用于多文件实现后的质量门禁及重构回归检查。

.claude/skills/dev-ultraqa/SKILL.md evolution-foundation/evo-nexus

Trigger Scenarios

多文件代码实现后合并前需要确保所有检查通过时涉及多个文件的重构以防回归

Install

npx skills add evolution-foundation/evo-nexus --skill dev-ultraqa -g -y

More Options

Non-standard path

npx skills add https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-ultraqa -g -y

Use without installing

npx skills use evolution-foundation/evo-nexus@dev-ultraqa

指定 Agent (Claude Code)

npx skills add evolution-foundation/evo-nexus --skill dev-ultraqa -a claude-code -g -y

安装 repo 全部 skill

npx skills add evolution-foundation/evo-nexus --all -g -y

预览 repo 内 skill

npx skills add evolution-foundation/evo-nexus --list

SKILL.md

Frontmatter

{
    "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:

Run build (npm run build, cargo build, go build)
Run lint (npm run lint, cargo clippy, golangci-lint)
Run tests (npm test, cargo test, pytest)
If green: done, exit cycle, hand off to @oath-verifier for final verification
If red: delegate to @bolt-executor or @hawk-debugger to fix the failure
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