dogfood

Name: dogfood
Availability: InStock
Author: Harries

Automate exploratory QA testing of web applications with browser tools and structured bug reports.

Updated Apr 24, 2026

Search Tags:#browser #test-automation #web-app #bug-report #qa-testing #exploratory-testing #evidence-capture

Ready to run

npx skills add https://github.com/Harries/hermes-agent --skill dogfood-harries

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Harries/hermes-agent/tree/main/skills/dogfood
Command: npx skills add https://github.com/Harries/hermes-agent --skill dogfood-harries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications to find bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

Phase-based exploratory QA workflow using a browser toolset to navigate, interact with elements, capture evidence (screenshots, console logs), and document findings.
Deterministic planning, exploration, and reporting phases that culminate in a formal bug report using a standardized issue taxonomy.
Output-driven testing with configurable inputs (target URL, testing scope, and output directory) to support repeatable tests and cross-project reuse.
Optional references to best-practices taxonomies and reproducible evidence collection.

Quick Start

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

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate exploratory QA testing for a web application?▼

Automated exploratory QA testing uses a browser toolset to systematically navigate web apps, interact with elements, and capture evidence. A deterministic workflow handles planning, exploration, issue categorization, and formal reporting to uncover bugs.

How do I capture and organize bug evidence during web app testing?▼

Bug evidence capture involves collecting screenshots and console logs during browser exploration, then saving them to a configurable output directory. This structured evidence collection supports repeatable tests and cross-project reuse for formal reporting.

Can I scope automated browser testing to a single page instead of a full-site audit?▼

Automated browser testing supports configurable testing scopes ranging from single pages to full-site audits. You provide a target URL and define the scope, allowing the workflow to adapt to specific testing boundaries.

What is a standardized issue taxonomy in QA reporting and when is it needed?▼

A standardized issue taxonomy in QA reporting is a classification system used to categorize discovered bugs during the reporting phase. It is needed when generating formal bug reports to ensure findings are structured and consistently documented.

Do I need to install browser plugins or dependencies to run automated web app QA?▼

No external dependencies or plugins are required to run automated web app QA. The skill operates independently using an integrated browser toolset to execute the exploratory testing workflow.

Does manual exploratory testing work better than a deterministic QA workflow?▼

Manual exploratory testing lacks the deterministic planning, exploration, and reporting phases that automate bug discovery. A deterministic QA workflow enforces a structured process with standardized issue taxonomy and reproducible evidence collection.