dogfood

Test web applications and capture reproducible bug evidence with screenshots.

3|Updated Apr 4, 2026

Search Tags:#testing #qa #browser automation #bug reporting #web applications #console errors

Ready to run

npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill dogfood-twjarviszyra-web

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically test web applications, discover bugs, capture evidence, and produce a clear report without relying on ad hoc manual notes.

Core Features & Use Cases

Exploratory QA Workflow: Follows a structured plan to inspect pages, navigate features, and test interactive elements.
Evidence Collection: Captures screenshots, console errors, and reproduction steps for each issue found.
Reporting and Triage: Organizes findings by severity and category, then generates a polished QA report for stakeholders.
Use Case: Use this Skill when validating a new site release, checking key user flows like signup or checkout, or documenting bugs for engineering review.

Quick Start

Ask the skill to test the target website, focus on the specified scope, and generate a structured QA report with screenshots and issue details.

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 web applications?▼

Exploratory QA testing for web applications involves systematically inspecting pages, navigation, forms, and interactive flows to find bugs. This skill structures that workflow by testing scoped browser sessions and capturing reproducible evidence like screenshots and console errors.

How do I generate a QA report with console errors and screenshots for bug triage?▼

Generating a QA report with console errors and screenshots requires capturing evidence during browser interaction and classifying issues by severity and category. This skill outputs a formatted report containing reproduction steps, screenshots, and issue taxonomy for engineering review.

What is the best way to test interactive web flows and edge cases for bug reporting?▼

Testing interactive web flows and edge cases for bug reporting requires a structured exploratory plan that navigates features and captures console errors. This skill scopes browser sessions to validate flows like signup or checkout and document discovered bugs.

Do I need browser automation tools to capture reproducible evidence for web testing?▼

Browser automation tools are required to capture reproducible evidence for web testing. This skill depends on browser interaction tools to inspect pages, capture screenshots, log console errors, and test interactive elements within scoped browser sessions.

Can I scope browser sessions to specific pages when validating a new site release?▼

You can scope browser sessions to specific pages when validating a new site release. This skill focuses exploratory QA on targeted areas like landing pages, forms, and interactive elements to systematically discover bugs and capture relevant evidence without testing the entire site.

Why does exploratory QA testing require issue taxonomy classification for stakeholders?▼

Exploratory QA testing requires issue taxonomy classification for stakeholders to organize findings by severity and category for effective triage. This skill generates a polished report that structures discovered bugs, reproduction steps, and evidence to inform engineering review decisions.