dogfood

Tests web applications via browser automation and generates structured bug reports with screenshots.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill dogfood-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/dogfood
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill dogfood-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual exploratory QA of web applications is slow and inconsistent, and bugs often ship without documented evidence. This Skill automates systematic browser-based testing, capturing console errors, screenshots, and reproducible steps for every issue found. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues by severity, and generate a final report. - Structured Issue Taxonomy: Classifies findings by severity (Critical/High/Medium/Low) and category (Functional, Visual, Accessibility, Console, UX, Content) using a reference taxonomy. - Evidence-Backed Reporting: Produces a Markdown report with an executive summary, per-issue reproduction steps, console errors, and inline screenshot references. - Use Case: Point the agent at a staging URL before a release; it navigates key flows, tests forms with valid and invalid inputs, checks the JS console after each interaction, and delivers a prioritized bug report. ## Quick Start Run exploratory QA on https://staging.example.com covering the signup and checkout flows and save the report to ./dogfood-output.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run automated exploratory QA on a web app?▼

Provide a target URL, a testing scope, and an optional output directory. The agent plans a sitemap, navigates each page with browser tools, interacts with elements, checks the console for errors, and saves a structured bug report with screenshots.

How to find JavaScript errors while testing a website?▼

The workflow calls browser_console after every navigation and significant interaction to surface uncaught exceptions, failed network requests, and deprecation warnings. These silent errors are recorded in the report under each related issue.

What tools does browser-based QA testing require?▼

It requires the browser toolset: browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. No external packages or scripts are needed beyond these tools.

How are bugs classified in the QA report?▼

Issues are assigned a severity (Critical, High, Medium, Low) and a category (Functional, Visual, Accessibility, Console, UX, Content) using the taxonomy in references/issue-taxonomy.md, then sorted by severity in the final report.

What are the limitations of automated exploratory testing?▼

It depends on the available browser toolset and cannot execute areas blocked by authentication or missing credentials, which are listed as blockers in the report. It complements rather than replaces scripted regression suites and load testing.