ultraqa
QA cycling workflow - test, verify, fix, repeat until goal met
Best use case
ultraqa is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. QA cycling workflow - test, verify, fix, repeat until goal met
QA cycling workflow - test, verify, fix, repeat until goal met
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "ultraqa" skill to help with this workflow task. Context: QA cycling workflow - test, verify, fix, repeat until goal met
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ultraqa/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ultraqa Compares
| Feature / Agent | ultraqa | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
QA cycling workflow - test, verify, fix, repeat until goal met
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# UltraQA Skill
[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]
## Overview
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 |
|------------|-----------|---------------|
| `/oh-my-claudecode:ultraqa --tests` | tests | All test suites pass |
| `/oh-my-claudecode:ultraqa --build` | build | Build succeeds with exit 0 |
| `/oh-my-claudecode:ultraqa --lint` | lint | No lint errors |
| `/oh-my-claudecode:ultraqa --typecheck` | typecheck | No TypeScript errors |
| `/oh-my-claudecode: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)
1. **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:
```
Task(subagent_type="oh-my-claudecode:qa-tester", model="sonnet", prompt="TEST:
Goal: [describe what to verify]
Service: [how to start]
Test cases: [specific scenarios to verify]")
```
2. **CHECK RESULT**: Did the goal pass?
- **YES** → Exit with success message
- **NO** → Continue to step 3
3. **ARCHITECT DIAGNOSIS**: Spawn architect to analyze failure
```
Task(subagent_type="oh-my-claudecode:architect", model="opus", prompt="DIAGNOSE FAILURE:
Goal: [goal type]
Output: [test/build output]
Provide root cause and specific fix recommendations.")
```
4. **FIX ISSUES**: Apply architect's recommendations
```
Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="FIX:
Issue: [architect diagnosis]
Files: [affected files]
Apply the fix precisely as recommended.")
```
5. **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 cycles
```
## State Tracking
Track state in `.omc/ultraqa-state.json`:
```json
{
"active": true,
"goal_type": "tests",
"goal_pattern": null,
"cycle": 1,
"max_cycles": 5,
"failures": ["3 tests failing: auth.test.ts"],
"started_at": "2024-01-18T12:00:00Z",
"session_id": "uuid"
}
```
## Cancellation
User can cancel with `/oh-my-claudecode:cancel` which clears the state file.
## Important Rules
1. **PARALLEL when possible** - Run diagnosis while preparing potential fixes
2. **TRACK failures** - Record each failure to detect patterns
3. **EARLY EXIT on pattern** - 3x same failure = stop and surface
4. **CLEAR OUTPUT** - User should always know current cycle and status
5. **CLEAN UP** - Clear state file on completion or cancellation
## STATE CLEANUP ON COMPLETION
**IMPORTANT: Delete state files on completion - do NOT just set `active: false`**
When goal is met OR max cycles reached OR exiting early:
```bash
# Delete ultraqa state file
rm -f .omc/state/ultraqa-state.json
```
This ensures clean state for future sessions. Stale state files with `active: false` should not be left behind.
---
Begin ULTRAQA cycling now. Parse the goal and start cycle 1.Related Skills
writer-memory
Agentic memory system for writers - track characters, relationships, scenes, and themes
visual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons
ultrawork
Parallel execution engine for high-throughput task completion
trace
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
team
N coordinated agents on shared task list using Claude Code native teams
skill
Manage local skills - list, add, remove, search, edit, setup wizard
setup
Use first for install/update routing — sends setup, doctor, or MCP requests to the correct OMC setup flow
sciomc
Orchestrate parallel scientist agents for comprehensive analysis with AUTO mode
release
Automated release workflow for oh-my-claudecode
ralplan
Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution
ralph
Self-referential loop until task completion with configurable verification reviewer
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions