Skill Claude CodeCodex
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.
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Collect and validate redacted, immutable QA evidence and evidence gaps for browser attempts. Use when capturing screenshots, traces, logs, telemetry, or explaining unavailable evidence.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Turn product requirements into traceable QA requirements and coverage obligations. Use when analyzing specifications, acceptance criteria, ambiguities, risks, or test scope.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Design deterministic, traceable browser test cases from approved requirements and coverage obligations. Use when creating, revising, parameterizing, or reviewing QA test cases.
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: