Deterministic, evidence-backed QA runtime for Codex, Claude Code, and Cursor. Versioned artifact contracts, Playwright browser driver, redacted evidence, reproducible release gates. Never calls an LLM.
Install and verify the QA Skills runtime in this project so the eight canonical QA skills become available. Use when the user asks to set up QA Skills, when qa-skill is missing or its runtime binding is broken, or when a QA skill stopped with setup guidance.
Execute approved bounded browser Test DSL cases with fresh isolated contexts and auditable attempts. Use when running browser tests, reruns, regression checks, or blocked execution diagnostics.
Generate deduplicated, reproducible QA bug reports only from failed product-defect attempts and registered evidence. Use when triaging failures, creating bug candidates, or preparing retest inputs.
Collect and validate redacted, immutable QA evidence and evidence gaps for browser attempts. Use when capturing screenshots, traces, logs, telemetry, or explaining unavailable evidence.
Generate an auditable QA execution report and deterministic release recommendation from registered run artifacts. Use when summarizing a QA run, reviewing release readiness, or rendering English or Vietnamese QA reports.
Coordinate a bounded, evidence-backed QA run from requirements through release recommendation. Use for end-to-end QA planning, execution, retests, regressions, or exploratory browser checks.
Turn product requirements into traceable QA requirements and coverage obligations. Use when analyzing specifications, acceptance criteria, ambiguities, risks, or test scope.
Prepare, bind, and clean up declared QA test data through trusted runtime hooks. Use when a test run needs fixtures, secret references, data setup, or cleanup verification.
Design deterministic, traceable browser test cases from approved requirements and coverage obligations. Use when creating, revising, parameterizing, or reviewing QA test cases.
★not rated 2 24d agoA36 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: