ultraqa
UltraQA automates the test-fix loop by running quality checks, analyzing what broke, and applying corrections across up to 5 cycles. Choose your goal—tests, build, lint, or type checking—and let it work toward success. It tracks progress, detects repeated failures, and exits when the goal is met or max cycles reached.
UltraQA runs automated QA cycles that diagnose and fix failures until your quality goal is met.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
UltraQA runs automated QA cycles that diagnose and fix failures until your quality goal is met. UltraQA automates the test-fix loop by running quality checks, analyzing what broke, and applying corrections across up to 5 cycles. Choose your goal—tests, build, lint, or type checking—and let it work toward success. It tracks progress, detects repeated failures, and exits when the goal is met or max cycles reached.
Use it when
- Yes.
- UltraQA executes a repeating cycle that verifies build, lint, typecheck, and tests in sequence.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
zereight/gitlab-mcp/ultraqa · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is ultraqa's automated testing workflow?
UltraQA automates the test-fix loop by running quality checks, analyzing what broke, and applying corrections across up to 5 cycles. You choose your goal—tests, build, lint, or type checking—and UltraQA works toward success, tracking progress and exiting when the goal is met or max cycles reached.
Can ultraqa fix all failing tests automatically?
Yes. UltraQA diagnoses and repairs test failures autonomously by running repeated QA cycles. It analyzes failure output, applies corrections, and re-runs tests until all pass or the maximum cycle limit is reached, eliminating manual debugging for each failure.
How does ultraqa's qa cycle run tests until pass?
UltraQA executes a repeating cycle that verifies build, lint, typecheck, and tests in sequence. After each run, it detects failures, diagnoses root causes, applies fixes, and loops again. The cycle continues until your chosen goal succeeds or you hit the 5-cycle maximum.
Does ultraqa fix lint errors automatically?
Yes. UltraQA includes lint verification in its automated quality assurance workflow. It detects lint failures, diagnoses issues, and applies corrections as part of its goal-based cycling process, working alongside test, build, and typecheck verification.
What quality checks does ultraqa cycle through?
UltraQA cycles through build verification, lint checking, TypeScript type checking, and test execution. It automates this entire workflow with goal-based exit conditions, repeating up to 5 times until your chosen quality target is met or the cycle limit is exhausted.
Is ultraqa released under an open-source license?
Yes. UltraQA is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
UltraQA
Autonomous QA cycling workflow that runs until your quality goal is met.
Cycle: run checks → diagnose failures → fix → repeat
Goal Types
| Flag | What to Check |
|---|---|
--tests |
All test suites pass |
--build |
Build succeeds with exit 0 |
--lint |
No lint errors |
--typecheck |
No TypeScript errors |
--interactive |
Interactive CLI/service testing via @qa-tester |
Cycle Workflow (Max 5)
- RUN QA: Execute verification based on goal type
- CHECK RESULT: Pass → exit success. Fail → continue
- DIAGNOSE: @architect analyzes failure, provides root cause
- FIX: @executor applies architect's recommendations
- REPEAT: Go back to step 1
Exit Conditions
- Goal Met: "ULTRAQA COMPLETE: Goal met after N cycles"
- Cycle 5 Reached: Exit with diagnosis
- Same Failure 3x: Exit early with root cause
- Environment Error: Exit with error
(truncated - see the full file via the links below)
File tree — 1 file
.github/skills/ultraqa/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Run automated QA cycles to fix failing tests until all pass”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
UltraQA automates quality assurance by cycling through test execution, failure diagnosis, and targeted fixes until your specified goal succeeds. It supports tests, builds, linting, type checking, or custom verification patterns, with a maximum of five cycles and early exit on repeated failures. The workflow coordinates diagnosis and remediation across multiple agents to streamline the path to passing quality gates.
Verify turns uncertain claims into concrete proof by running existing tests, type checks, and targeted validation commands. It reports exactly what passed, what failed, and what remains unverified—ensuring changes are genuinely complete before you move on.
tdd guides you through strict test-driven development using the red-green-refactor cycle: write a failing test, implement minimal code to pass it, then refactor. The skill enforces the discipline of writing tests before production code and provides framework-specific commands for multiple languages.
Status displays which OMG mode is running and reports its current progress, including active phases, task completion, and agent states. Use it to verify what's executing, monitor advancement through workflows, or confirm state after resuming operations.
Trace systematically investigates why something happened by generating competing hypotheses and evaluating evidence for and against each one. It's built for ambiguous causal questions—runtime bugs, performance regressions, and architecture issues—where you need to explain the most likely explanation. The skill structures your investigation through observation, hypothesis generation, evidence gathering, and discriminating probes.
Testing Strategies covers the testing pyramid—unit tests for speed and breadth, integration tests for component interaction, and E2E tests for full-system validation. Learn Arrange-Act-Assert structure, mocking patterns, edge case handling, and database testing with real examples using Jest, Playwright, and Testcontainers.
More skills Test-Driven Development (TDD) (MIT)