dogfood

Find defects in web applications through exploratory QA testing with evidence capture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you perform structured exploratory QA on web applications, turning ad hoc browsing into a repeatable process for finding defects, capturing evidence, and producing clear bug reports.

Core Features & Use Cases

  • Systematic Web Testing: Plan, explore, and validate pages, navigation paths, forms, and edge cases across a target site.
  • Evidence Collection: Capture screenshots, console errors, and reproduction steps for each issue you discover.
  • Report Generation: Produce a severity-ranked QA report with summaries, issue details, and testing coverage notes.
  • Use Case: A tester can assess a login flow, checkout flow, or full site pass and deliver a structured report the product team can act on immediately.

Quick Start

Use the dogfood skill to test this web app at the provided URL, focus on the specified scope, and produce a full bug report with screenshots and reproduction steps.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform exploratory QA testing on a web application?

Exploratory QA testing on a web application involves systematically navigating browser-based product flows, checking edge cases, and capturing console errors to find defects. This process turns ad hoc browsing into a repeatable method for discovering bugs.

What is the best way to document web app bugs with reproduction steps?

Documenting web app bugs requires capturing screenshots, recording console errors, and detailing reproduction steps during browser navigation. This evidence collection ensures each discovered defect is clearly documented for the product team to review and resolve.

Can I generate a severity-ranked bug report for a checkout flow?

Yes, you can generate a severity-ranked bug report for a checkout flow by inspecting end-to-end user journeys, capturing visual evidence, and logging defects. The resulting QA report summarizes issue details and testing coverage for immediate action.

Does systematic QA testing work for validating navigation paths and edge cases?

Systematic QA testing works effectively for validating navigation paths and edge cases across browser-based web applications. It applies structured exploratory techniques to plan, explore, and validate user journeys to uncover hidden defects.

How do I capture console errors and screenshots during web testing?

Capturing console errors and screenshots during web testing requires browser navigation, visual inspection, and evidence collection for each issue discovered. This ensures all defects are accompanied by visual proof and reproduction steps for accurate reporting.

What are the limitations of exploratory QA testing for web applications?

Exploratory QA testing for web applications is limited to browser-based product flows such as navigation, forms, and end-to-end user journeys. It relies on visual inspection and console checks, meaning it may not detect non-UI backend defects or performance bottlenecks.