ultraqa
Skill5 starsChanged 17 days agoMITView on GitHub
QA cycling workflow - test, verify, fix, repeat until goal met
5 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- listener-He/java-harness-agenttheir own version, first seen Oct 20, 2026
- zereight/gitlab-mcpedited, first seen Oct 8, 2026
- Yeachan-Heo/oh-my-codextheir own version, first seen Oct 8, 2026
- Jurel89/copilot-omnitheir own version, first seen Apr 17, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- zereight/gitlab-mcp★ 2.1k34% same
Wrote their own version · 4
- Yeachan-Heo/oh-my-codex★ 34ksame name
- listener-He/java-harness-agent★ 16same name
- Yomudogly/oh-my-agy★ 4same name
- Jurel89/copilot-omni★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository119 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibilitySkill
- frontend-designSkill
- python-background-jobsSkill
- python-executorSkill
- python-testing-patternsSkill
- seoSkill
- ai-slop-cleanerSkill
- analyzeSkill
- api-and-interface-designSkill
- ask-claudeSkill
- ask-geminiSkill
- autopilotSkill
- browser-testing-with-devtoolsSkill
- build-fixSkill
- cancelSkill
- ci-cd-and-automationSkill
- clawd-change-workflowSkill
- code-review-and-qualitySkill
- code-reviewSkill
- code-simplificationSkill
- configure-notificationsSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deep-interviewSkill
- deepsearchSkill
- deprecation-and-migrationSkill
- doctorSkill
- documentation-and-adrsSkill
- ecomodeSkill
- frontend-ui-engineeringSkill
- frontend-ui-uxSkill
- git-masterSkill
- git-workflow-and-versioningSkill
- helpSkill
- hudSkill
- idea-refineSkill
- incremental-implementationSkill
- intent_routerSkill
- keyword_registrySkill
- mode_stateSkill
- noteSkill
- omx-setupSkill
- performance-optimizationSkill
- pipeline_orchestratorSkill
- pipelineSkill
- planning-and-task-breakdownSkill
- planSkill
- ralph-initSkill
- ralph_loopSkill
- ralphSkill
- ralplanSkill
- android-reverse-engineeringSkill
- api-securitySkill
- apk-reverseSkill
- attack-chainSkill
- binary-diffSkill
- browser-automationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.
- Distinctive: line 15
Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.
- Distinctive: line 16
If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the QA cycle is …
- Distinctive: line 35
If no structured goal provided, interpret the argument as a custom goal.
- Very specific: line 101
Use omx_state MCP tools for UltraQA lifecycle state.
- Distinctive: line 130
PARALLEL when possible: - Run diagnosis while preparing potential fixes
- Very specific: line 138
When goal is met OR max cycles reached OR exiting early, run $cancel or call:
- Distinctive: line 142
Use MCP state cleanup rather than deleting files directly.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UltraQA Skill
[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]
Overview
GPT-5.4 Guidance Alignment
- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.
- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.
- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the QA cycle is grounded.
- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.
You are now in ULTRAQA mode - an autonomous QA cycling workflow that runs until your quality goal is met.
Cycle: qa-tester → architect verification → fix → repeat
Goal Parsing
Parse the goal from arguments. Supported formats:
| Invocation | Goal Type | What to Check |
/ultraqa --tests | tests | All test suites pass |
/ultraqa --build | build | Build succeeds with exit 0 |
/ultraqa --lint | lint | No lint errors |
/ultraqa --typecheck | typecheck | No TypeScript errors |
/ultraqa --custom "pattern" | custom | Custom success pattern in output |
If no structured goal provided, interpret the argument as a custom goal.
Cycle Workflow
Cycle N (Max 5)
- RUN QA: Execute verification based on goal type
--tests: Run the project's test command--build: Run the project's build command--lint: Run the project's lint command--typecheck: Run the project's type check command--custom: Run appropriate command and check for pattern--interactive: Use qa-tester for interactive CLI/service testing:delegate(role="qa-tester", tier="STANDARD", task="TEST: Goal: [describe what to verify] Service: [how to start] Test cases: [specific scenarios to verify]")
- CHECK RESULT: Did the goal pass?
- YES → Exit with success message
- NO → Continue to step 3
- ARCHITECT DIAGNOSIS: Spawn architect to analyze failure
delegate(role="architect", tier="THOROUGH", task="DIAGNOSE FAILURE: Goal: [goal type] Output: [test/build output] Provide root cause and specific fix recommendations.") - FIX ISSUES: Apply architect's recommendations
delegate(role="executor", tier="STANDARD", task="FIX: Issue: [architect diagnosis] Files: [affected files] Apply the fix precisely as recommended.") - REPEAT: Go back to step 1
Exit Conditions
| Condition | Action |
| Goal Met | Exit with success: "ULTRAQA COMPLETE: Goal met after N cycles" |
| Cycle 5 Reached | Exit with diagnosis: "ULTRAQA STOPPED: Max cycles. Diagnosis: ..." |
| Same Failure 3x | Exit early: "ULTRAQA STOPPED: Same failure detected 3 times. Root cause: ..." |
| Environment Error | Exit: "ULTRAQA ERROR: [tmux/port/dependency issue]" |
Observability
Output progress each cycle:
[ULTRAQA Cycle 1/5] Running tests...
[ULTRAQA Cycle 1/5] FAILED - 3 tests failing
[ULTRAQA Cycle 1/5] Architect diagnosing...
[ULTRAQA Cycle 1/5] Fixing: auth.test.ts - missing mock
[ULTRAQA Cycle 2/5] Running tests...
[ULTRAQA Cycle 2/5] PASSED - All 47 tests pass
[ULTRAQA COMPLETE] Goal met after 2 cyclesState Tracking
Use omx_state MCP tools for UltraQA lifecycle state.
- On start:
state_write({mode: "ultraqa", active: true, current_phase: "qa", iteration: 1, started_at: "<now>"}) - On each cycle:
state_write({mode: "ultraqa", current_phase: "qa", iteration: <cycle>}) - On diagnose/fix transitions:
state_write({mode: "ultraqa", current_phase: "diagnose"})state_write({mode: "ultraqa", current_phase: "fix"}) - On completion:
state_write({mode: "ultraqa", active: false, current_phase: "complete", completed_at: "<now>"}) - For resume detection:
state_read({mode: "ultraqa"})
Scenario Examples
Good: The user says continue after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.
Good: The user changes only the output shape or downstream delivery step (for example make a PR). Preserve earlier non-conflicting workflow constraints and apply the update locally.
Bad: The user says continue, and the workflow restarts discovery or stops before the missing verification/evidence is gathered.
Cancellation
User can cancel with /cancel which clears the state file.
Important Rules
- PARALLEL when possible - Run diagnosis while preparing potential fixes
- TRACK failures - Record each failure to detect patterns
- EARLY EXIT on pattern - 3x same failure = stop and surface
- CLEAR OUTPUT - User should always know current cycle and status
- CLEAN UP - Clear state file on completion or cancellation
STATE CLEANUP ON COMPLETION
When goal is met OR max cycles reached OR exiting early, run $cancel or call:
state_clear({mode: "ultraqa"})
Use MCP state cleanup rather than deleting files directly.
Begin ULTRAQA cycling now. Parse the goal and start cycle 1.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

