dogfood

Navigate web pages, interact with elements, and capture visual and console evidence for bug reports.

1|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill dogfood-icyzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/icyzh/hermes-web/tree/main/skills/software-development/dogfood
Command: npx skills add https://github.com/icyzh/hermes-web --skill dogfood-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of performing consistent, thorough exploratory testing on web applications by providing a structured, repeatable workflow for identifying bugs and capturing evidence.

Core Features & Use Cases

  • Systematic Exploration: Guides the AI through a 5-phase testing process including planning, navigation, interaction, evidence collection, and reporting.
  • Automated Reporting: Generates a professional, formatted bug report including severity, steps to reproduce, and console error logs.
  • Use Case: Use this skill to perform a comprehensive smoke test on a new deployment, ensuring that all key user flows, forms, and navigation elements function correctly across the application.

Quick Start

Initiate a full exploratory QA session on the target website by providing the URL and the desired testing scope to the agent.

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 is performed by navigating pages, interacting with elements, and capturing visual and console evidence. This skill structures the process into a 5-phase workflow for consistent bug detection.

Can I automate smoke tests for a new web deployment?

You can automate smoke tests for new web deployments by running a full exploratory QA session on the target URL. The agent systematically validates key user flows, forms, and navigation elements to ensure correct functionality.

What is the best way to capture console error logs during web UI testing?

The best way to capture console error logs during web UI testing is through evidence collection phases that record console-based diagnostics alongside visual captures. This ensures comprehensive bug reporting with reproducible error logs.

Does exploratory web testing require browser toolset access?

Exploratory web testing requires browser toolset access to execute navigation, interaction, and diagnostic commands. This environment access is necessary to comprehensively test diverse web interfaces and user flows.

What types of bugs can systematic web testing identify?

Systematic web testing identifies functional, visual, and accessibility bugs across diverse web interfaces and user flows. It captures evidence to generate professional reports detailing severity and steps to reproduce.

How are bug reports formatted after a QA testing session?

Bug reports after a QA testing session are formatted automatically with severity levels, steps to reproduce, and captured console error logs. This structured reporting provides professional, actionable feedback for developers.