Use recorded test statuses to prepare a release check summary.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Group recorded outcomes for a defined release check period.
/oo BugBug: List all BugBug test run pages started between [start] and [end]. Group by status and summarize test name, run ID, start time, duration and result link when present. Flag failed and error runs without inventing root causes.
Launch a specified test and report its actual execution status.
/oo BugBug: Find BugBug test [name or UUID] and inspect its details. Run it using profile [name or UUID, or default] with variable overrides [list, or none]. Keep the run ID and check its status. Report the result link; if it is still pending, say so rather than claiming it passed.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with the BugBug API token from your integration settings.
Connect BugBug →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Read tests, suites, run profiles and execution history from BugBug. You can summarize failures in a chosen period or start an existing test and check the resulting run status.
Read test metadata, suite membership and run profile options.
Read execution history, start existing tests and check statuses.
List tests available in the connected BugBug workspace.
Leina 
Wanta 
bugbug.list_tests Retrieve details for a specific BugBug test by ID.
bugbug.get_test List suites available in the connected BugBug workspace.
bugbug.list_suites Retrieve details for a specific BugBug suite by ID.
bugbug.get_suite List run profiles available for executing BugBug tests.
bugbug.list_profiles List historical BugBug test runs with optional filters.
bugbug.list_test_runs Execute a BugBug test using the official RunTest request contract.
bugbug.run_test Retrieve the current status of a BugBug test run by ID.
bugbug.get_test_run_status No matching tools.
Run records identify status and link to the BugBug result. They do not include detailed step failure evidence, so a root-cause explanation needs additional information.
Yes. Suite details include linked tests and settings such as retry count, parallel execution and run profile. The connection does not launch an entire suite.
It reads existing definitions and runs existing tests. Recording or creating a new test is not included.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.