dogfood

Execute systematic exploratory QA testing on web applications with structured bug reports.

2|1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/heysuhas/hermes_cli --skill dogfood-heysuhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/heysuhas/hermes_cli/tree/main/skills/dogfood
Command: npx skills add https://github.com/heysuhas/hermes_cli --skill dogfood-heysuhas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of inconsistent and manual exploratory testing by providing a structured, repeatable framework for identifying, documenting, and reporting web application issues.

Core Features & Use Cases

  • Systematic Exploration: Guides the AI through a 5-phase workflow covering planning, navigation, interaction, evidence collection, and reporting.
  • Automated Evidence Capture: Automatically generates annotated screenshots and console logs to provide clear, actionable bug reports.
  • Use Case: Use this skill to perform a comprehensive smoke test on a new feature deployment, ensuring that all interactive elements, form validations, and navigation flows are functioning correctly across the application.

Quick Start

Initiate a full exploratory QA session on the target website by providing the URL and the specific features you want to test.

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 5-phase workflow covering planning, navigation, interaction, evidence collection, and reporting to systematically identify functional, visual, and accessibility issues across your web application.

What is the best way to perform a smoke test on a new web deployment?

The best way to perform a smoke test on a new web deployment is using a structured exploratory testing framework that verifies interactive elements, form validations, and navigation flows while automatically capturing console logs and annotated screenshots as evidence.

How does systematic browser testing capture bug report evidence?

Systematic browser testing captures bug report evidence by executing browser-based navigation, interaction, and console monitoring to automatically generate annotated screenshots and structured logs with clear, actionable details.

Do I need a specific browser toolset to run automated web QA sessions?

Yes, automated web QA sessions require a browser toolset capable of snapshotting, clicking, typing, and capturing visual state to properly execute the interaction and evidence collection phases.

Can I use systematic QA testing to find accessibility issues on my website?

Yes, you can use systematic QA testing to find accessibility issues on your website because the exploratory testing workflow is specifically designed to identify functional, visual, and accessibility problems during navigation and interaction.

Why does exploratory web testing need a structured 5-phase workflow?

Exploratory web testing needs a structured 5-phase workflow to solve the challenge of inconsistent manual testing by providing a repeatable framework for systematically identifying, documenting, and reporting web application issues.