Skip to content

rlaope/oh-my-hermes / skills/ulw-qa

ulw-qa

Verified

[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.

Ultraqa

This is a Hermes-native ultraqa workflow skill.

Why This Exists

ultraqa exists because behavior that passes its own tests can still fail under inputs and conditions nobody wrote down: it turns the changed behavior and known risks into hostile scenarios, records each one's observed pass or fail apart from any proposed fix, and hands fixes to the selected coding executor.

Do Not Use When

  • Exploratory bug-hunting across a web app with no changed behavior to attack; on Hermes, use the bundled dogfood skill when it is available, and bring a finding back here as a scenario to reproduce.
  • Judging whether a rendered page, image, or terminal frame looks right across viewports and states; use omh-visual-qa.
  • Confirming that a finished change meets its acceptance criteria with the smallest proving check, when no hostile scenarios are wanted; use omh-verification-gate.

Examples

Good example:

  • Prompt: $ultraqa test the setup wizard with hostile install paths, stale config, and missing PATH cases.
  • Expected behavior: Generate adversarial QA scenarios, expected signals, observed results, and fix-or-retry routing.
  • Why: The request asks for verification pressure and hostile scenarios.

Bad example:

  • Prompt: ultraqa that the profile page looks right on mobile
  • Expected behavior: Route to omh-visual-qa; no changed behavior is being attacked.
  • Why: The question is how a rendered page looks, which the viewport and state matrix answers.

Completion Checklist

  • The scenario, expected behavior, observed result, and pass/fail basis are named.
  • Proposed fixes are separated from observed QA evidence.
  • Missing or failed verification routes back to omh-plan, fix, or a narrower test; a failed scenario gets at most two fix-and-rerun rounds, then it is reported as an open finding with its evidence and is not redefined to pass.
  • Everything the hostile scenarios created or changed (accounts, rows, files, processes, ports) was listed before the first one ran and removed or restored afterwards, with the command and its observed result as the cleanup receipt, or what remains is named.

Recovery Notes

  • If a scenario needs a real install or external service the harness cannot reach, retain other observed pass/fail evidence, mark that scenario not_observed, and hand back its manual test guide with setup, do, expect, and broken signals.
  • If a hostile browser scenario would submit, buy, send, or delete on a live target without approval, retain read-only scenario results, mark that action not_observed, and hand back the target and exact action for user approval.
  • If a failing browser scenario has no screenshot or console readback, keep its observed failure, mark diagnosis tentative, and hand back the scenario, target, and missing capture for a bounded rerun.

Workflow Lane

  • Current lane: Coding handoff - coding owners, handoffs, review, CI, and merge evidence.
  • If intent belongs to another lane, hand back to omh-routing or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

When to Use

Use when the task needs adversarial test scenarios, verification, and fix loops.

Strong routing signals: `ultraqa`, `$ultraqa`, `adversarial qa`, `hostile scenarios`, `e2e qa`, `real-world qa`, `qa scenario`, `release qa`, `敵対的QA`, `リリース前QA`, `障害シナリオ`, `장애 상황`, `쿠버네티스 장애`, `적절히 진단`, `검증 체크리스트`, `릴리즈 전 gate`, `злые сценарии`, `прогони e2e`, `e2e сценарий`, `e2e тест`, `адверсариальное тестирование`, `对抗式测试`, `发布前测试`, `故障场景`, `uji skenario ekstrem`, `lakukan QA adversarial`, `uji skenario kegagalan sebelum rilis`, `bantu cari celah lewat pengujian end to end`, `uji aplikasi dengan kondisi pengguna nyata`, `jalankan siklus pengujian dan perbaikan berulang`, `kiểm thử các tình huống cực đoan`, `tiến hành QA phản biện`, `kiểm thử các tình huống thất bại trước khi phát hành`, `giúp tìm lỗ hổng qua kiểm thử end to end`, `kiểm thử ứng dụng với điều kiện người dùng thực tế`, `chạy các chu kỳ kiểm thử và sửa lỗi lặp lại`

Catalog Metadata

Category: verification Phase: qa Hermes role: reviewer Quality tier: scenario-gated Reasoning demand: standard

Quality bar:

  • Do not start this engine as an automatic continuation of another skill's output: an accepted plan, a clarified brief, or a routing recommendation is planning evidence, not permission. Unless the user explicitly invoked this engine themselves, restate in one line what will start (engine, scope, selected executor) and wait for the user's explicit go-ahead first.
  • A mid-run user message is an interjection, not a stop: answer it briefly and, in the same reply, continue the run — re-read the phase todo when one is active and dispatch or advance the next pending step, or name the armed wait it is waiting on -- handle, bound completion signal, deadline -- instead of re-reading status. Only the user's explicit stop or cancel, or the engine's own completion gate, ends the run; when the interjection changes scope, say so and update the declared plan or todo instead of silently abandoning it. A mid-run message is the latest steering for the active task, not automatically a replacement objective: it replaces the objective when the user says so and steers the current one otherwise.
  • A follow-up that needs new authority, materially expands the scope, or changes external state not already authorized is described first and started only on the user's approval: the turn ends by naming that next action and asking whether to take it, as one question carrying the choices the user has, never by declaring what will not be done; persistence never broadens the authorized scope. A refused escalation is answered the same way, with a safer alternative inside the boundary or the authorization the boundary asks for — never a workaround or an indirect execution.
  • The closing brief scales to the change: one or two sentences for a simple change. Lead with the result and validation; omit abandoned approaches unless they explain a tradeoff, and internal bookkeeping. Disclose requested-but-not-done work and material prepared/unmerged work; omit unrelated non-action footers. Required accounting stays outside this scaling. Order: result -> relevant evidence/limits -> observed accounting (when required) -> specific question (if useful). For a real unresolved user decision or a useful briefing discussion, offer one specific, content-linked question. Completed work needs no question; discussion grants no authority. Never estimate usage.
  • Generate hostile scenarios from changed behavior and known risk areas.
  • Report pass/fail evidence separately from proposed fixes.
  • For native omh_todo checkpoints, load omh-todo-checklist/references/closing-a-story.md; record then recall this qa declaration. Stored declarations are not proof.
  • Delegate code mutations discovered by QA to the selected coding executor.
  • A check no automation can hold gets a manual test guide, never a done claim: load references/manual-test-guide.md for the step shape (setup, do, expect, broken), the four reasons a step may stay manual, and why it stays prepared_not_observed until a run records a fresh observed_check_results/v1. code-story phase VI. Manual test guide; rendered surfaces go to omh-visual-qa.
  • For probes that must run in Hermes-owned isolation or outlive this session, load references/board-fanin.md: one probe row per scenario in its own worktree, one fixer row whose parents is every probe, re-verification through the review lane, and findings only through bounded readback.
  • When Hermes owns the coding path, read hermes_coding_harness/v1 before saying build, verification, review, docs, or PR-prep evidence exists.
  • On a web app, when browser_vision is in your tool list or tool_search finds it, run each hostile scenario through the session's browser tools against the target the user named (local or staging unless stated), and a scenario that would submit, buy, send, or delete on a live surface waits for the user's approval; read browser_console after every navigation and interaction, and keep a failing scenario's screenshot_path and console errors as its observed evidence.

Handoff policy:

Hermes can design scenarios and report observed results; code fixes discovered by QA should become selected executor/runtime handoffs.

Required inputs:

  • changed behavior
  • acceptance criteria
  • known risk areas

Expected outputs:

  • adversarial scenarios
  • pass/fail evidence
  • fix recommendations

Artifact expectations:

  • QA scenario evidence
  • runtime verification summary

Safety rules:

  • Do not imply hidden Hermes runtime behavior.
  • Use the smallest verification that can prove the claim.

Runtime Evidence

Preferred harness for this skill: qa-specialist.

omh runtime record --skill ultraqa --harness qa-specialist --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • When wrapper metadata includes memory_review_card/v1 or handoff_context_pack/v1, treat it as reviewed OMH-local or wrapper-supplied context only. Use conflict-free context summaries to shape plans and handoffs, but do not claim Hermes internal memory was read or changed. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only. When the requested output is delivered, put any open points inside the result and end with no question or offer; only when the person asked to choose or decide and that choice is still theirs, end with one specific question about it, not a list, a generic offer, or a footer; the shared rail's Reply Language And Host Voice and Turn Ending sections hold the full rule.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md'). Load it when applicable; otherwise name an unavailable capability.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall