agentleFS
YomudoglyYomudogly/oh-my-agy/skills/ultraqa/SKILL.md

ultraqa

Skill4 starsChanged todayMITView on GitHub

[oh-my-agy] Adversarial dynamic end-to-end QA: build a hostile scenario matrix, run baseline + adversarial scenarios, diagnose, fix, clean up, and report, in up to 5 bounded cycles. Use for $ultraqa (--tests, --build, --lint, --typecheck, --interactive, --custom \"pattern\") when runnable behavior needs more than a shallow test checklist.

5 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Use this explicit opt-in when runnable behavior needs adversarial dynamic end-to-end QA.

    line 8
  2. Very specific:

    If the user says continue, advance the current verified QA step rather than restarting.

    line 14
  3. Very specific:

    Before running commands, record a matrix (in .omagy/artifacts/ultraqa-<slug>/matrix.md) with: scenario id, class, trigger status (triggered …

    line 20

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UltraQA Task Card

Use this explicit opt-in when runnable behavior needs adversarial dynamic end-to-end QA. This card defines the QA matrix, evidence contract, and bounded cycling.

When to use and inputs

  • Goals: --tests, --build, --lint, --typecheck, --interactive, or --custom "pattern". Without a structured goal, derive a runnable behavior goal.
  • Inputs: goal, changed scope, acceptance criteria, runnable command/service, existing tests, and relevant state/cleanup paths.
  • If the user says continue, advance the current verified QA step rather than restarting.
  • A shallow build/lint/typecheck/test checklist does not satisfy UltraQA. Exercise the requested behavior through adversarial scenarios whenever it can be run, simulated, or harnessed safely.
  • Standalone vs. Embedded Ownership: when invoked standalone ($ultraqa), the current agent executes the QA matrix directly; when embedded inside $autopilot or $ultragoal, the orchestrator delegates QA scenario execution to an independent subagent worker (test-engineer, verifier, or executor) and verifies its evidence rather than self-grading its own implementation in the main lane.

Plan and trigger-mapped scenario matrix

Before running commands, record a matrix (in .omagy/artifacts/ultraqa-<slug>/matrix.md) with: scenario id, class, trigger status (triggered or not-applicable: <1-line reason>), intent, user/attacker model, setup, command or harness, expected signal, actual result, failure_class (none | product | harness), fixes, evidence, and cleanup. Evaluate all 9 adversarial classes against their concrete trigger conditions:

#Adversarial ClassTrigger Condition (run when true; otherwise log 1-line not-applicable)Probes
1Malformed inputCode parses user, CLI, file, network, JSON, or env inputInvalid JSON, missing fields, bad flags, oversized strings, unusual Unicode, path traversal (../), corrupted state
2Prompt injectionCode ingests untrusted text, prompts, transcripts, or external contentInstruction overrides, secret exfiltration strings, verification-skip payloads, fake completion claims
3Cancel / resumeWorkflow persists state, checkpoints, or supports stop/resumeMid-run abort, resume from partial state, idempotent re-entry, $cancel cleanup
4Stale stateCode reads cached state, lockfiles, timestamps, or session IDsExpired timestamps (> STALE_MS), foreign owner_conversation_id, schema-version mismatch, contradictory phases
5Dirty worktreeCode runs git commands, file generators, or cleanup stepsPre-existing modified/untracked files outside scope remain untouched after run and rollback
6Hung or long-running commandsCode spawns child processes, network calls, or loopsBounded timeout, clean process termination (manage_task kill), no orphan processes
7Flaky testsAsync timing, concurrency, temp files, or randomness in testsCapped reruns (3x), shared-state isolation, deterministic ordering (a single lucky green does not count)
8Misleading success outputCLI/hook/API returns status text or exit codesNon-zero exit with "PASS" text, zero exit with "ERROR"/test.skip, partial output truncation
9Repeated interruptionsInteractive loop, hook nudge, or retry state machineRepeated continue, rapid duplicate invocations, retry budget exhaustion

Cycle (maximum 5)

  1. PLAN ADVERSARIAL QA: goal, success criteria, safety bounds, stop condition, runnable surfaces, matrix.
  2. RUN BASELINE VERIFICATION: --tests runs the project tests; --build runs the build plus built-artifact probes; --lint; --typecheck plus typed harnesses; --custom checks the pattern and exit status; --interactive uses a bounded CLI/service or browser harness following references/browser-verification-safety.md (await document.fonts.ready + double requestAnimationFrame render settle, console/network 4xx/5xx triage, and OWASP LLM01 untrusted DOM/cookie quarantine).
  3. RUN ADVERSARIAL SCENARIOS: pre-scan custom harness scripts and teardown commands with sh <plugin>/hooks/run.sh lookout <paths> --json (exitCode: 0 required before execution), then capture exit codes, output, artifacts, and cleanup. Use run_command with a bounded WaitMsBeforeAsync for long runs, and manage_task kill for hung processes.
  4. CHECK RESULT: pass only when baseline, adversarial scenarios, evidence, and cleanup all pass. Otherwise diagnose and repeat.
  5. ARCHITECT DIAGNOSIS (via the architect or debugger subagent for non-trivial failures): root cause and safety impact. FIX ISSUES precisely. CLEAN UP AND ROLL BACK temporary harnesses, fixtures, logs, processes, state, and failed experiments before the next cycle.

Generate temporary tests, scripts, fixtures, or harnesses only when useful. Keep them under .omagy/artifacts/ultraqa-<slug>/ or the project's test directories. Use bounded runtimes and project-native tools. Write harness files with write_file / write_to_file (not interpolating heredocs). Use absolute repo paths in harness imports. Classify harness setup failures as harness debris: fix the harness and rerun before declaring a product defect.

Safety, state, and exit

No destructive commands, secret exfiltration, credential dumping, production writes, or unbounded process spawning. No unbounded waits. Preserve unrelated dirty work. If a scenario is unsafe, record it as blocked along with the safe substitute. Normalized Repeated-Failure Deduplication: normalize failure output via sh <plugin>/hooks/run.sh failure-sig "<errorOutput>" (which strips ANSI escape codes, pytest/vitest dot-progress & pass-summary lines, Start at clock timestamps, elapsed duration parentheticals & failing summary banner durations, and Node warning PIDs while preserving assertion literals) before comparing across cycles; three repeats of the same normalized failure signature stop the loop immediately with a diagnosis (ULTRAQA STOPPED: Same failure detected 3 times). Cycle 5 stops with residual risks. Success exits after a passing cycle.

State: standalone writes .omagy/state/ultraqa-state.json; inside Autopilot, use state.ultraqa and current_phase:"ultraqa". Phases: planning -> baseline -> adversarial-e2e -> diagnose -> fix -> cleanup -> complete. Update iteration, current_phase, and updated_at as you go (the Stop hook keeps an active run going). Terminal: active:false, current_phase:"complete"|"failed"|"blocked", completed_at.

Evidence/output contract

Return # UltraQA Report with: Goal and success criteria (stop condition, safety bounds); Scenario matrix (all columns); Commands run (exit code, purpose, timeout, key output); Failures found (root cause, user/safety impact); Fixes applied (files, rationale, scenarios, regression evidence); Cleanup and rollback (artifacts/processes/worktree before and after); Residual risks; Evidence (logs, harness output, screenshots where relevant, rerun/flake evidence).

Exit condition

ULTRAQA COMPLETE: Goal met after N cycles only after a passing baseline plus adversarial matrix, clean artifacts, and complete evidence. Otherwise return the exact bounded status: ULTRAQA STOPPED: Max cycles, ULTRAQA STOPPED: Same failure detected 3 times, ULTRAQA BLOCKED: ..., or ULTRAQA ERROR: ..., with the owner and next safe step.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.