dogfood

Name: dogfood
Availability: InStock
Author: cabezno

Guide exploratory QA testing of web applications with evidence capture and structured bug reports.

Updated May 15, 2026

Search Tags:#qa automation #bug reporting #exploratory testing #issue classification #web browser #screenshot evidence #javascript console

Ready to run

npx skills add https://github.com/cabezno/bmb-encover-agent --skill dogfood-cabezno

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/dogfood
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill dogfood-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of missing functional, visual, console, and UX issues in web applications by guiding consistent exploratory testing and producing evidence-backed bug reports.

Core Features & Use Cases

Systematic exploratory QA: Plans a sitemap/scope, navigates pages, interacts with UI elements, and checks expected behavior across key user flows.
Evidence collection: Captures DOM snapshots, console output, and annotated screenshots for each observed issue.
Structured reporting: Classifies issues by severity/category using the provided taxonomy and generates a complete report from a template.

Quick Start

Run the dogfood skill to test a target web URL end-to-end and generate a bug report with screenshots in the 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 exploratory testing for a web application to find UI and console bugs?▼

Exploratory testing for web apps requires navigating user flows and checking console output. This skill guides a 5-phase workflow using browser-driven navigation and evidence capture to uncover functional, visual, and console anomalies across a specified scope.

What is the best way to capture screenshot evidence and JavaScript console errors during QA automation?▼

Capturing screenshot evidence and JavaScript console errors during QA automation requires systematic evidence collection. This skill captures DOM snapshots, console output, and annotated screenshots for each observed issue to produce evidence-backed bug reports.

How do I classify and report web application defects using a structured taxonomy?▼

Classifying and reporting web application defects requires a structured taxonomy and standardized templates. This skill classifies issues by severity and category using a provided taxonomy, then generates a complete report from a template while saving artifacts to an output directory.

Can I use this systematic QA workflow for testing web forms and edge cases across different user flows?▼

Yes, systematic QA workflows can test web forms and edge cases across user flows. This skill targets web pages, forms, and edge cases by planning a sitemap scope and interacting with UI elements to verify expected behavior.

Do I need to provide an output directory when generating bug reports from exploratory testing?▼

Yes, you need to provide an output directory when generating bug reports. The skill saves all collected artifacts, including annotated screenshots and DOM snapshots, to your chosen output directory during the report generation phase.