dogfood

Identify and document web application quality issues from exploratory testing.

Updated May 1, 2026

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

Ready to run

npx skills add https://github.com/xiaoquqi/hermes-agent-skills --skill dogfood-xiaoquqi

💬 Prompt for ChatGPT / Claude Chat▼

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

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

Guided browser-based exploration to assess page integrity, interactivity, and accessibility.
Evidence collection and structured bug report generation with an executive summary.
Real-world scenarios: regression testing across critical user flows and pages.

Quick Start

Navigate to the target URL, methodically explore core pages and interactions, capture evidence, and generate a structured bug report.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate exploratory web testing to capture evidence and generate bug reports?▼

Exploratory web testing can be automated by navigating target URLs, methodically interacting with page elements, capturing evidence of quality issues, and generating a structured bug report with severity classifications and recommended fixes.

What is structured exploratory testing for web applications?▼

Structured exploratory testing is a QA process that systematically assesses web page integrity, interactivity, and accessibility across typical user flows to uncover bugs and document them with reproducible evidence.

Can I use this for regression testing across critical user flows?▼

Yes, you can perform regression testing by methodically exploring critical web pages and user interactions, collecting evidence of integrity or accessibility issues, and documenting them in a structured report.

How do I classify bug severity when documenting web application quality issues?▼

Bug severity is classified during the report generation phase, where uncovered web application quality issues are detailed with an issue taxonomy classification, severity level, and recommended fixes in an executive summary.

Does browser-based QA testing require specific dependencies or components?▼

Browser-based QA testing requires no specific dependencies or components, allowing you to directly navigate URLs, interact with elements, and collect evidence for your structured bug reports.

What is the best way to document web page interactivity and accessibility issues?▼

The best way to document these issues is through guided browser-based exploration that captures reproducible evidence, classifies the issue taxonomy, and generates a comprehensive executive summary with recommended fixes.