dogfood

Guide structured exploratory QA testing of web applications and generate bug reports.

Updated Apr 10, 2026

Search Tags:#automation #qa #evidence #web-testing #browser #ux #bug-report

Ready to run

npx skills add https://github.com/KarlinskyS/hermesSkills --skill dogfood-karlinskys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/KarlinskyS/hermesSkills/tree/main/dogfood
Command: npx skills add https://github.com/KarlinskyS/hermesSkills --skill dogfood-karlinskys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications to uncover bugs, capture evidence, and generate structured reports, reducing time to identify issues and communicate findings across teams.

Core Features & Use Cases

Structured QA workflow: plan, explore, collect evidence, categorize, and report bugs.
Browser-based testing across typical flows: landing pages, navigation, forms, interactivity, and error states.
Automated artifact collection: screenshots, console logs, and final report generation for any target URL.

Quick Start

Provide a target URL and testing scope, then run the dogfood workflow to automatically test and capture a structured QA report.

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 to capture web application bugs?▼

To automate QA testing for web application bugs, provide a target URL and testing scope to trigger structured exploratory testing. The workflow automatically captures screenshots, console logs, and generates a structured report.

What is structured exploratory QA testing for web applications?▼

Structured exploratory QA testing is a systematic process of navigating browser-based user flows to uncover bugs. It involves planning, exploring pages and interactions, collecting evidence like console logs, and categorizing findings into a final report.

How do I collect evidence for a bug report during browser testing?▼

You collect evidence for a bug report during browser testing by running an automated workflow that captures screenshots and console logs. This requires defining a testing scope and providing an output directory for the artifacts.

Do I need a specific browser toolset to run exploratory QA workflows?▼

Yes, you need access to a browser toolset and a defined output directory for artifacts to run the exploratory QA workflows. The testing applies to browser-based interactions across landing pages, navigation, forms, and error states.

What is the best way to test web application user flows for error states?▼

The best way to test web application user flows for error states is using a systematic QA workflow that guides exploration across typical interactions. It automatically captures evidence and produces a structured report to communicate findings.

What testing scope is required to generate a structured QA report?▼

A defined testing scope and a target URL are required to generate a structured QA report. The scope guides the exploratory testing across specific pages, forms, interactivity, and error states to ensure relevant evidence collection.