dogfood

Systematically QA web applications and generate structured bug reports.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gqf2008/hermez-ai --skill dogfood-gqf2008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/gqf2008/hermez-ai/tree/main/skills/dogfood
Command: npx skills add https://github.com/gqf2008/hermez-ai --skill dogfood-gqf2008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA testing of web applications using a browser toolset to identify issues, capture evidence, and generate structured bug reports.

Core Features & Use Cases

  • Guided, phase-based QA workflow across pages and user flows
  • Evidence capture, annotated screenshots, and organized bug reporting
  • Reproducible testing routines for common tasks like navigation, form interaction, and error handling

Quick Start

Provide a target URL and testing scope to start your systematic QA session.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate QA testing for web applications to find bugs systematically?

Automate QA testing by applying a phase-based workflow that plans exploratory tests, interacts with web pages via browser tools, collects evidence, and generates structured bug reports.

What is the best way to capture evidence and generate bug reports during web testing?

The best way to capture evidence for bug reports is to use a structured workflow that annotates screenshots and logs interactions during web testing, organizing them into reproducible routines.

Can I use this for regression checks on complex web applications?

Yes, you can use this for regression checks on complex web applications. It systematically verifies navigation, form interactions, and error handling workflows across various application sizes.

How do I start a structured web testing session for exploratory testing?

To start a structured web testing session, provide a target URL and define the testing scope. The workflow then guides you through planning, exploring, and categorizing identified issues.

Does web QA testing require any specific browser tool dependencies?

No specific browser tool dependencies are required. The workflow applies standard browser-tool commands to interact with web elements and capture evidence without needing external modules.

What limitations exist when testing web applications with a phase-based workflow?

Limitations include reliance on browser-tool commands for evidence collection, meaning testing is confined to web application interfaces and standard navigation workflows rather than backend systems.