dogfood

Guide exploratory QA testing of web applications with browser navigation and evidence capture.

Updated May 16, 2026
One-click install
npx skills add https://github.com/jaredcroxton/hermes-mirror --skill dogfood-jaredcroxton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/jaredcroxton/hermes-mirror/tree/main/agents/skills/dogfood
Command: npx skills add https://github.com/jaredcroxton/hermes-mirror --skill dogfood-jaredcroxton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Dogfood eliminates the guesswork of exploratory QA by guiding you to systematically navigate a web app, verify behavior, capture concrete evidence, and turn findings into a structured bug report.

Core Features & Use Cases

  • Systematic exploratory workflow: Plans a sitemap from a user-provided scope, explores each page/feature, and iteratively tests interactions.
  • Evidence-first debugging: Captures screenshots and annotated visual assessments, and records console output after navigations and significant interactions.
  • Structured, taxonomy-based reporting: Classifies each issue by severity and category (Functional/Visual/Accessibility/Console/UX/Content) and generates a final report using a template.
  • Use case: When launching or validating a feature (e.g., login, checkout, search), this skill helps produce a reproducible report with URLs, steps to reproduce, expected vs actual behavior, and screenshot evidence.

Quick Start

Ask Hermes to run dogfood against a target URL for a full-site scope and save results to ./dogfood-output.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run exploratory QA testing for a web app?

Exploratory QA testing involves systematically navigating a web app to identify functional, visual, accessibility, and console issues. You need a browser toolset to interact with flows, capture screenshot evidence, and generate a structured bug report.

What is the best way to collect reproducible evidence during browser testing?

Collecting reproducible evidence during browser testing requires capturing screenshots and recording JavaScript console output after navigations and interactions. This ensures bug reports include concrete visual assessments and verified console errors.

How do I structure bug reports from web accessibility and functional tests?

Structure bug reports by classifying issues into categories like Functional, Visual, Accessibility, and Console. Include URLs, steps to reproduce, expected versus actual behavior, and screenshot evidence within a final template.

Can I use browser toolset commands to check JavaScript console errors during QA?

Yes, you can use browser toolset commands to check JavaScript console errors during QA. The testing workflow specifically records console output after navigations and significant interactions to identify hidden issues.

Does exploratory QA testing work for testing planned user flows and edge cases?

Exploratory QA testing works effectively for planned user flows and edge cases. It plans a sitemap from your provided scope, iteratively tests interactions across pages and forms, and ensures repeatable coverage.

Why should I classify web app issues by severity during bug reporting?

Classifying web app issues by severity during bug reporting prioritizes fixes based on impact. It organizes functional, visual, and accessibility defects systematically, making the final report actionable for developers.