mabl-debugDiagnose and fix failures detected by mabl end-to-end tests. Forensic inspection of an already-failed run (`mabl agent debug steps`, `mabl agent debug artifact`) plus an interactive live session that re-runs the test step-by-step in a real Chrome attached to the agent via CDP (`mabl agent debug sess
mabl-initOne-time project setup for mabl. Discover this user's mabl workspace, applications, environments, and credentials over the mabl MCP server, then save everything an AI agent needs to create and run mabl cloud tests where the user wants it — an agent memory file (CLAUDE.md / AGENTS.md / .github/copilo
mabl-test-authoringCreate a SINGLE mabl browser or API test through conversational planning and cloud authoring. Plan one test with an AI agent, refine the plan iteratively, initiate cloud (or local) test generation, then validate that the test it built actually matches what you asked for and fix it if not. Fire when
mabl-test-coverage-designUse when asked to create MULTIPLE mabl tests / a whole suite for a feature area — "add mabl coverage for X", "cover the X page/feature with mabl tests", "design a mabl test suite for X", "let's create tests for X", "explore X and create tests", or "/mabl-test-coverage-design". For testing a page, sc
mabl-test-edit-verifyCERTIFIES an edit already made to a mabl test, without trusting the green run. NOT for reporting what changed between two versions — that is mabl-version-compare, which states the diff and leaves the verdict alone. This one holds the intent and rules on it. Diffs against the version before the chang
mabl-test-editChange a mabl test that already exists — rename it, relabel it, enable/disable it, or edit its steps (replace, insert, delete, move). Reads the test, then routes to the cheapest lane that can make the change deterministically — a live browser agent only when it needs the running app. Fire when the u
mabl-test-impactFind, screen, run, and report on the EXISTING mabl end-to-end tests covering a product-code change, after unit tests pass and before opening a PR, or check what already covers an area. For designing NEW coverage for an area use mabl-test-coverage-design; for a test your change intentionally broke us
mabl-version-compareReport what changed between two versions of a mabl test or reusable flow, or between two of them, separating changes that alter behaviour from ones that only reorganize: steps added / removed / changed / moved, assertion counts by type, strictness (exact match to substring, a check no longer gating)