dogfood

Run automated exploratory QA tests on web apps and generate structured bug reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides QA teams through systematic exploratory testing of web applications, helping reveal bugs, gather evidence, and generate structured reports quickly.

Core Features & Use Cases

  • Guided 5-phase workflow (Plan, Explore, Collect Evidence, Categorize, Report) to structure manual QA with browser tools
  • Automated evidence capture and structured bug reporting to accelerate triage and fixes
  • Adversarial/edge-case scenarios by design to reveal usability and reliability gaps

Quick Start

Provide a target URL to Hermes and start the automated dogfood QA workflow to generate a structured report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
What is exploratory QA testing for web applications?▼

Exploratory QA testing for web applications is a simultaneous learning and test design process. This skill automates it by guiding a browser through adversarial scenarios to uncover usability and reliability gaps in staging environments.

How do I automate bug hunting and evidence collection for a staging environment?▼

Automate bug hunting and evidence collection by providing a target URL to start the guided workflow. The skill uses built-in browser actions to explore web apps, automatically capturing evidence to accelerate triage.

Can I use this for structured bug reporting on web apps?▼

Yes, you can use this for structured bug reporting on web apps. It enforces a five-phase workflow ending in categorize and report phases, generating evidence-based tickets to accelerate triage and fixes.

What is the best way to structure manual QA with browser tools?▼

The best way to structure manual QA with browser tools is using a five-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. This structure ensures edge-case scenarios reveal real issues quickly.

Does automated exploratory testing work for edge-case scenarios?▼

Automated exploratory testing works for edge-case scenarios by design. The workflow applies adversarial scenarios against web applications to proactively reveal usability and reliability gaps during exploration.