dogfood

Explore web applications to identify defects and generate structured reports.

1|Updated Apr 30, 2025

Search Tags:#testing #qa #reporting #evidence #browser #web #bug-report

Ready to run

npx skills add https://github.com/lucasfth/config --skill dogfood-lucasfth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/lucasfth/config/tree/main/.hermes/skills/dogfood
Command: npx skills add https://github.com/lucasfth/config --skill dogfood-lucasfth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

A five-phase workflow (Plan, Explore, Collect Evidence, Categorize, Report) to guide rigorous testing.
Prerequisites include a browser toolset and a defined target URL and testing scope.
Outputs a comprehensive report with issue taxonomy and evidence.
Use Case: Ensure critical paths are validated across multiple pages and interactions, with reproducible evidence for each bug.

Quick Start

Provide a target URL and scope, then start the dogfood workflow to begin exploratory testing and produce the final report.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I systematically find bugs in a web application and capture evidence?▼

Systematic web QA testing identifies defects by exploring critical user flows, capturing screenshots and console data, and generating structured reports. A five-phase workflow guides planning, exploration, evidence collection, categorization, and reporting to ensure reproducible bug documentation.

What's the best way to generate structured QA reports with console data and screenshots?▼

Structured QA reports are generated by collecting browser console data and screenshots during web exploration. Captured evidence is categorized into an issue taxonomy, producing a comprehensive report that validates critical paths across multiple pages and interactions.

Do I need a browser toolset to perform exploratory web testing?▼

Yes, exploratory web testing requires a browser toolset to interact with the target URL. You must also define a testing scope and an output directory to orchestrate the planning, exploration, and evidence collection phases effectively.

Can I use systematic QA testing to validate critical user flows across multiple pages?▼

Yes, systematic QA testing validates critical user flows across multiple pages and interactions. By defining a target URL and scope, the testing workflow explores from landing pages through complex paths, capturing reproducible evidence for each identified defect.

How does systematic exploratory testing categorize and report identified defects?▼

Exploratory testing categorizes defects by collecting evidence throughout the exploration phase and organizing it into a structured issue taxonomy. This process yields a comprehensive final report detailing reproducible issues with corresponding screenshots and console data.

Why do I need to define a testing scope and output directory for web QA?▼

Defining a testing scope and output directory is required to orchestrate the QA workflow. The scope guides the systematic exploration of the target URL, while the directory stores captured screenshots, console data, and the final structured bug report.