dogfood

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

5|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AjayRajan05/VoiceOS --skill dogfood-ajayrajan05
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/AjayRajan05/VoiceOS/tree/main/skills/bundled/community/dogfood
Command: npx skills add https://github.com/AjayRajan05/VoiceOS --skill dogfood-ajayrajan05

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, explore, collect evidence, categorize, and report on web application issues using browser automation tools. - Evidence Capture: Takes annotated screenshots, monitors JavaScript console errors, and records reproduction steps for every bug. - Structured Bug Reports: Classifies issues by severity (Critical/High/Medium/Low) and category (Functional/Visual/Accessibility/Console/UX/Content), then generates a formatted Markdown report. - Use Case: Point the Skill at a staging URL before a release; it navigates pages, clicks elements, fills forms with valid and invalid inputs, and delivers a prioritized bug report with screenshot evidence. ## Quick Start Ask the assistant to dogfood-test your web app at a given URL with a defined scope and save the bug report to an output directory.

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 and testing scope, and the Skill follows a 5-phase workflow: plan a sitemap, explore pages with browser automation, collect screenshot and console evidence, categorize issues by severity, and generate a Markdown bug report.

How are bugs classified in automated QA reports?▼

Issues are classified by severity (Critical, High, Medium, Low) and category (Functional, Visual, Accessibility, Console, UX, Content) using a defined taxonomy. Reports are sorted by severity with counts summarized in an executive summary.

What browser tools are required for automated web testing?▼

The Skill requires a browser toolset including navigate, snapshot, click, type, scroll, back, press, vision (screenshot with AI analysis), and console monitoring. Without these tools available, the testing workflow cannot execute.

Can automated QA detect JavaScript console errors?▼

Yes, the workflow checks the browser console after every navigation and significant interaction. Silent JavaScript errors, uncaught exceptions, failed network requests, and deprecation warnings are captured and included in the report.

What are the limitations of automated exploratory testing?▼

Automated exploration depends on the defined scope and may miss areas not in the test plan, such as authenticated flows without credentials or payment flows. The report documents untested areas and blockers explicitly.