dogfood

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

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

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 and produces a structured, severity-classified bug report. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Plan, explore, collect evidence, categorize, and report on web app issues using browser automation tools. - Evidence Capture: Takes annotated screenshots and records console errors, reproduction steps, and expected versus actual behavior for every issue. - Issue Classification: Applies a defined taxonomy of severity levels (Critical to Low) and categories (Functional, Visual, Accessibility, Console, UX, Content). - Use Case: Point the agent at a staging URL before a release, and receive a report.md with deduplicated, severity-sorted bugs, inline screenshot evidence, and a coverage summary. ## Quick Start Run a full dogfood QA pass on https://staging.myapp.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 testing on a web app?▼

Provide a target URL, a testing scope such as full site or specific flows, and optionally an output directory. The agent navigates pages, interacts with elements, checks the console, captures screenshots, and writes a structured report.md with classified issues.

What browser tools are needed for automated web testing?▼

This workflow requires a browser toolset exposing browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. Without these tools available, the testing phases cannot execute.

How are bugs classified in a QA report?▼

Issues are assigned a severity of Critical, High, Medium, or Low and a category of Functional, Visual, Accessibility, Console, UX, or Content. The taxonomy in references/issue-taxonomy.md defines concrete examples for each level, and issues are deduplicated and sorted by severity.

Can automated browser testing detect JavaScript console errors?▼

Yes, the workflow checks browser_console after every navigation and significant interaction to catch silent JS errors, uncaught exceptions, failed network requests, and CORS or mixed-content warnings. These are recorded as evidence in the report.

What are the limitations of exploratory browser-based QA?▼

It depends on the availability of the browser toolset and only covers pages reachable through navigation within the defined scope. Areas behind authentication or blocked by critical bugs are documented in the report's blockers section rather than tested.