What problem does it solve? Turning a folder of WebMobAI scenario JSON files into a trustworthy CI build gate is error-prone: wrong binaries exit 0 on failure, tag typos silently skip tests, and traces never make it into uploaded artifacts. This Skill wires suites, parallelism, sharding, reporters, and exit codes correctly. ## Core Features & Use Cases - Suite authoring and execution: Builds suite JSON files with tags, defaults, and inline or path-based scenario entries, then runs them with webmobai-suite using --workers, --shard, --tag, and --reporter flags. - CI pipeline wiring: Produces a complete GitHub Actions workflow with Playwright browser installation, webmobai-doctor preflight, JUnit XML publishing, and artifact upload including per-scenario trace.zip files. - Exit code discipline: Explains the 0/1/2 exit semantics of webmobai-suite, webmobai-scenario, and webmobai-doctor, and why webmobai-test must never gate a build. - Use Case: A team has 12 scenario files and wants a GitHub Actions gate that fails pull requests. This Skill generates the suite file, a 4-shard matrix workflow, JUnit reporting via dorny/test-reporter, and the sessionDir copy step that archives Playwright traces. ## Quick Start Ask the AI to set up your WebMobAI scenario files as a sharded GitHub Actions gate with JUnit reporting and trace artifact uploads.
