dogfood

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

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill dogfood-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/skills/dogfood
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill dogfood-chensihakniroth

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 — covering navigation, forms, interactive elements, and edge cases across the target site. - Automated Evidence Capture: Takes annotated screenshots and monitors the JavaScript console after every interaction to surface silent errors. - Structured Bug Reports: Classifies issues by severity (Critical to Low) and category (Functional, Visual, Accessibility, Console, UX, Content), then generates a report with an executive summary and summary table. - Use Case: Point the agent at a staging URL before a release; it navigates key user flows, tests form validation with invalid inputs, and delivers a report.md with screenshot evidence for each bug. ## Quick Start Run exploratory QA testing on https://staging.myapp.com covering the signup and checkout flows and save the bug 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 specific features or full site, and optionally an output directory. The agent follows a 5-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues, and generate a report.

How to detect JavaScript console errors during website testing?▼

The browser_console tool is called after every navigation and significant interaction to capture uncaught exceptions, failed network requests, and deprecation warnings. These silent errors are recorded as findings and included in the final bug report.

What does the dogfood QA report include?▼

The report contains an executive summary with issue counts by severity, per-issue sections with reproduction steps and screenshot references, a summary table, and testing coverage notes listing pages tested, features exercised, and any blockers encountered.

How are bugs classified by severity in automated QA?▼

Issues are classified using a defined taxonomy: Critical for unusable core features or data loss, High for significantly impaired functionality, Medium for noticeable UX problems, and Low for minor polish issues. Categories include Functional, Visual, Accessibility, Console, UX, and Content.

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

This approach depends on the availability of the browser toolset and only covers what is reachable through navigation and interaction. Areas behind authentication walls without credentials, performance under load, and backend logic are out of scope and noted as untested in the report.