dogfood

Test web applications and generate structured QA bug reports with evidence.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/davpatel605-beep/hermusagent --skill dogfood-davpatel605-beep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/davpatel605-beep/hermusagent/tree/main/backend/vendor/hermes/skills/dogfood
Command: npx skills add https://github.com/davpatel605-beep/hermusagent --skill dogfood-davpatel605-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams discover and document defects in web applications by replacing ad hoc testing with a structured exploratory QA process.

Core Features & Use Cases

  • Exploratory Browser Testing: Navigate web applications, inspect pages, test interactions, and identify functional, visual, accessibility, and console issues.
  • Evidence-Based Bug Reporting: Capture screenshots, reproduction steps, expected versus actual behavior, and severity classifications for discovered issues.
  • Use Case: QA engineers can run a full website review to uncover broken flows, UI problems, JavaScript errors, and usability issues before release.

Quick Start

Use the dogfood skill to test the provided web application URL and generate a structured QA bug report with evidence.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I find and document web application bugs through exploratory testing?

Exploratory testing finds web application bugs by navigating web pages, testing interactions, and identifying functional, visual, and accessibility issues. This process replaces ad hoc testing with structured QA to systematically uncover defects before release.

What is the best way to generate structured bug reports with reproduction steps and severity?

Generating structured bug reports involves capturing screenshots, detailing reproduction steps, and classifying issue severity. This evidence-based approach documents expected versus actual behavior to clearly communicate defects found during web application testing.

Do I need browser automation capabilities to run systematic QA testing on web applications?

Browser automation capabilities are required to run systematic QA testing on web applications. These tools capture evidence, classify issues, and navigate interactive features, enabling comprehensive testing of navigation flows, forms, and responsive checks.

Can I test responsive checks and usability reviews for browser-based web applications?

Responsive checks and usability reviews are fully supported for browser-based web applications. This testing approach evaluates interactive features, navigation flows, and page layouts to identify visual problems, console errors, and usability issues.

What types of web application defects can systematic exploratory quality assurance testing uncover?

Systematic exploratory quality assurance testing uncovers functional, visual, accessibility, and console issues within web applications. It identifies broken navigation flows, UI problems, JavaScript errors, and usability defects by inspecting pages and testing interactions.

How does structured exploratory QA testing compare to ad hoc testing for finding web app defects?

Structured exploratory QA testing replaces ad hoc testing by applying a systematic process to discover and document web application defects. This ensures comprehensive coverage of navigation flows and interactive features, yielding reliable evidence-based bug reports.