dogfood

Tests web applications via browser automation and generates structured bug reports with screenshots.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/i-bebsi/hermes-agent --skill dogfood-i-bebsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/i-bebsi/hermes-agent/tree/main/hermes-config/skills/dogfood
Command: npx skills add https://github.com/i-bebsi/hermes-agent --skill dogfood-i-bebsi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually exploring a web application to find bugs is slow and inconsistent, and issues are often reported without evidence or severity classification. This Skill runs a systematic five-phase exploratory QA workflow that navigates pages, interacts with elements, captures screenshots and console errors, and produces a structured bug report. ## Core Features & Use Cases - Systematic Exploration: Plans a sitemap, navigates pages, clicks elements, fills forms, and checks keyboard navigation using the browser toolset. - Evidence Collection: Captures annotated screenshots and JavaScript console errors after every interaction, classifying each issue by severity (Critical to Low) and category (Functional, Visual, Accessibility, Console, UX, Content). - Structured Reporting: Generates a report with an executive summary, per-issue reproduction steps, a summary table, and testing coverage notes. - Use Case: Point the agent at a staging URL before a release, and receive a prioritized bug report with screenshot evidence and console errors for every issue found. ## Quick Start Ask the agent to dogfood-test https://staging.example.com focusing on the signup and checkout flows and save the report to ./dogfood-output.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run automated exploratory QA testing on a web app?▼

Provide a target URL and testing scope, and the agent follows a five-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot and console evidence, categorize issues by severity, and generate a structured report.

What browser tools are needed for automated web testing?▼

The workflow requires browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. These cover navigation, DOM inspection, interaction, screenshots, and console error detection.

How are bugs classified in a QA report?▼

Issues are assigned a severity (Critical, High, Medium, Low) and a category (Functional, Visual, Accessibility, Console, UX, Content) based on a defined taxonomy. Critical issues break core features or cause data loss, while Low issues are minor polish problems.

Can automated testing detect JavaScript console errors?▼

Yes, the workflow checks the browser console after every navigation and significant interaction. Silent JavaScript errors, failed network requests, and unhandled promise rejections are captured and included in the report as evidence.

What are the limitations of exploratory browser-based QA?▼

It depends on the availability of the browser toolset and only covers what the agent can reach through the UI. Areas behind authentication it cannot complete, or flows blocked by critical bugs, are listed as blockers in the report.