dogfood

Automate exploratory QA testing of web applications with structured bug reports and screenshots.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/danmartinez78/echo-ghost-backup --skill dogfood-danmartinez78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/danmartinez78/echo-ghost-backup/tree/main/skills/dogfood
Command: npx skills add https://github.com/danmartinez78/echo-ghost-backup --skill dogfood-danmartinez78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Systematic exploratory QA testing of web applications to uncover bugs, collect evidence, and produce structured reports efficiently.

Core Features & Use Cases

  • Plan, Explore, and Report: orchestrates a five-phase QA workflow including planning, exploration, evidence collection, issue categorization, and reporting.
  • Evidence-first Reporting: captures screenshots, console logs, and DOM states to support reproducible bug reports.
  • Scope-flexible Testing: operates on full-site tests or targeted pages with browser toolsets.

Quick Start

Provide a target URL and testing scope to begin automated exploratory QA.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory QA testing for a web application?

Automated exploratory QA testing for a web application is orchestrated through a five-phase workflow: planning, exploration, evidence collection, issue categorization, and reporting. You provide a target URL and testing scope to initiate the browser-based process.

What is the best way to capture UI bug evidence during web testing?

The best way to capture UI bug evidence during web testing is an evidence-first approach that automatically records screenshots, console logs, and DOM states. This ensures bug reports are fully reproducible with attached contextual data.

Can I run targeted browser testing on specific pages instead of a full site?

Yes, you can run targeted browser testing on specific pages instead of a full site. The scope-flexible testing feature operates on both full-site tests and targeted pages using browser toolsets to discover navigation issues and regression gaps.

Does this web QA workflow require specific browser toolset commands?

Yes, this web QA workflow requires browser toolset commands for navigation, interaction, evidence capture, and reporting. These commands drive the automated exploration and structured bug report generation.

Why use automated exploratory testing over manual QA for websites?

Automated exploratory testing reveals bugs fast by applying a systematic workflow to manual testing efforts. It uncovers UI bugs and regression gaps across websites while automatically attaching screenshots and console logs to structured reports.