muggle-testlisted

Change-driven E2E acceptance testing with Muggle AI: detect the user's recent code changes (local diff or a PR), map them to affected user flows, run real-browser tests on localhost or a preview/staging URL, publish results, and post a screenshot summary to the PR. Use whenever the user wants to test, validate, or regression-test their own in-progress changes or work — "make sure I didn't break anything", "did my recent commits break any user flows?", "test before I push" — especially as the acceptance gate before opening or merging a PR. The defining signal is change-driven validation tied to a commit, push, PR, or merge. For one specific named feature/flow use muggle-test-feature-local; not for importing existing tests, configuring preferences, or replaying a single named script.
multiplex-ai/muggle-ai-works · ★ 16 · Testing & QA · score 63

Install: claude install-skill multiplex-ai/muggle-ai-works

# Muggle Test — Change-Driven E2E Acceptance Router > Telemetry first step: see [`_shared/telemetry-emit.md`](../_shared/telemetry-emit.md). Use `skillName: "muggle-test"`. A router skill that detects code changes, resolves impacted test cases, executes them locally or remotely, reads the cloud results from the Muggle AI dashboard (local runs are published by the studio during execution; remote runs publish cloud-side), and posts E2E acceptance summaries to the PR. The user can invoke this at any moment, in any state. ## UX Guidelines — Minimize Typing **Every selection-based question MUST use the `AskUserQuestion` tool** (or the platform's equivalent structured selection tool). Never ask the user to "reply with a number" in a plain text message — always present clickable options. - **Selections** (project, use case, test case, mode, approval): Use `AskUserQuestion` with labeled options the user can click. - **Multi-select** (use cases, test cases): Use `AskUserQuestion` with `allow_multiple: true`. - **Free-text inputs** (URLs, descriptions): Only use plain text prompts when there is no finite set of options. Even then, offer a detected/default value when possible. - **Batch related questions**: If two questions are independent, present them together in a single `AskUserQuestion` call rather than asking sequentially. - **Parallelize job-creation calls**: Whenever you're kicking off N independent cloud jobs — creating multiple use cases, generating/creating multiple test