Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yeachan-heo/ultraqa
QA cycling workflow - test, verify, fix, repeat until goal met
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 8 more in the full report
11 fixed8 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just refactored our database connection layer and need you to autonomously run the test suite, diagnose any failures that pop up, apply patches, and repeat the verification loop until all unit tests pass. Please display progress updates for each cycle.
| Checked | Without skill | With skill |
|---|---|---|
| Displays cycle progress output using the standard bracketed ULTRAQA format | Missed | Passed |
The instructions your model reads when the skill loads.
[ULTRAQA ACTIVATED - AUTONOMOUS QA CYCLING]
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, Ralph, Team, and UltragoalUltraQA owns repeated quality-gate cycling only. Use the deterministic conflict policies refuse, adopt_existing, and artifact_only rather than non-deterministic warning handling. Use it after the target behavior is known and the remaining question is whether tests, build, lint, typecheck, or another explicit QA condition passes. If Claude Code /goal is active, UltraQA may produce visible command evidence for that goal, but must not describe the /goal evaluator as independently running commands or reading files. If Ralph or Team is active, UltraQA is a verification/fix sub-loop under that authority rather than a competing session loop. If no active loop is safe, record QA expectations and evidence in artifact-only Ultragoal notes instead of claiming automatic execution.
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.
--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:
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.