dogfood

Execute exploratory QA testing of web apps and generate structured bug reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often spend excessive time manually detecting issues across complex web applications. This skill standardizes exploratory testing, helping you systematically uncover bugs, gather evidence, and convert findings into a structured report.

Core Features & Use Cases

  • End-to-end exploration workflow: Plan, explore, collect evidence, categorize, and report to ensure comprehensive coverage.
  • Evidence capture & reporting: Navigate pages, interact with elements, record console messages, take annotated screenshots, and assemble a formal bug report.
  • Use Case: A QA engineer tests a new web app across critical flows, documents issues, and shares a reproducible report with stakeholders.

Quick Start

Provide a target URL and testing scope, then run the dogfood workflow to begin exploratory QA testing.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform exploratory QA testing on a web application?

Exploratory QA testing on a web application is executed by planning, exploring, interacting with elements, collecting evidence, and assembling a structured report to uncover bugs fast.

Can I generate a structured bug report with annotated screenshots?

Yes, structured bug reports with annotated screenshots are generated by navigating pages, interacting with elements, recording console messages, and assembling formal documentation for stakeholders.

What do I need to start testing browser-based interfaces for edge cases?

To start testing browser-based interfaces for edge cases, you need a browser toolset with capabilities like navigate, click, type, snapshot, and vision to capture evidence effectively.

Does this QA testing workflow support diverse web apps or specific frameworks?

This QA testing workflow supports diverse web apps by focusing on critical flows, interactive elements, and edge cases across browser-based interfaces rather than targeting specific frameworks.

Why does manual QA testing take so long for complex web applications?

Manual QA testing takes excessive time because detecting issues across complex web applications lacks standardization, requiring systematic exploratory workflows to gather evidence and generate reports efficiently.