dogfood

Execute exploratory browser-driven test flows and output structured bug reports.

Updated Apr 9, 2026

Search Tags:#browser automation #test coverage #bug reporting #console errors #exploratory testing #web qa #evidence screenshots

Ready to run

npx skills add https://github.com/MarbleSodas/Mavis --skill dogfood-marblesodas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/dogfood
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill dogfood-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams discover real-world web application issues by running a repeatable exploratory QA process that collects evidence and produces structured bug reports.

Core Features & Use Cases

Systematic exploratory testing across pages, flows, forms, and edge cases (including navigation and 404s).
Evidence capture with DOM snapshots, annotated visual walkthroughs, and screenshot references for every issue.
Bug classification and reporting with severity/category guidance and a ready-to-ship markdown report.

Quick Start

Tell the agent the target URL, the testing scope you want (or say “full site”), and where you want the output saved, and it will produce a complete QA report with screenshot evidence.

Frequently Asked Questions about dogfood

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run exploratory testing on a web app and collect evidence?▼

Exploratory testing for web apps is executed by driving browser flows across user journeys, forms, and navigation links, then capturing evidence like DOM snapshots and annotated screenshots to produce structured bug reports.

How do I capture console errors and screenshots for bug reporting?▼

Console errors and visual anomalies are captured during browser-driven test flows using browser tool capabilities for console inspection and screenshot-based reporting, compiling the findings into a structured markdown report with severity classification.

Can I test web accessibility and edge cases like 404s across a specific URL scope?▼

Yes, exploratory testing can systematically uncover visual and accessibility anomalies, navigation 404s, and form edge cases across a specified URL scope, outputting a complete QA report with screenshot references for every issue.

What is the best way to find web app bugs through browser automation?▼

Browser automation finds web app bugs by executing repeatable exploratory test flows that inspect the DOM and console, categorize defects by severity, and generate a ready-to-ship markdown report with screenshot evidence.

Do I need browser tool capabilities to generate evidence-backed QA reports?▼

Yes, browser tool capabilities for navigation, snapshots, console inspection, visual analysis, and screenshot-based reporting are required to systematically uncover defects and output a structured QA report with evidence.