dogfood

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

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill dogfood-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/dogfood
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill dogfood-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual exploratory QA testing of web applications is time-consuming and inconsistent, and bugs often go undocumented without screenshots, reproduction steps, or severity classification. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues by severity, and generate a final report. - Structured Issue Taxonomy: Classifies every finding by severity (Critical/High/Medium/Low) and category (Functional, Visual, Accessibility, Console, UX, Content) using a defined reference taxonomy. - Evidence-Backed Reporting: Produces a Markdown report with an executive summary, per-issue reproduction steps, console errors, and inline screenshot references. - Use Case: Point the agent at a staging URL before a release; it navigates key user flows, tests forms with valid and invalid inputs, checks the JS console for silent errors, and delivers a prioritized bug report. ## Quick Start Run exploratory QA testing on https://staging.example.com covering 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 application?▼

Provide a target URL and testing scope, then the skill follows a 5-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues, and generate a structured Markdown report.

How to find JavaScript errors during website testing?▼

The skill checks the browser console after every navigation and significant interaction using browser_console. Silent JS errors, uncaught exceptions, and failed network requests are captured and classified as Console-category issues in the report.

What tools are required for browser-based QA testing with this skill?▼

It requires the browser toolset: browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, browser_press, and browser_close. No external packages are needed.

How are bugs classified in the QA report?▼

Each issue gets a severity (Critical, High, Medium, Low) and a category (Functional, Visual, Accessibility, Console, UX, Content) based on the taxonomy in references/issue-taxonomy.md, then sorted Critical-first in the report.

What are the limitations of automated exploratory web testing?▼

It depends on what the browser tools can reach and observe; areas behind authentication it cannot complete, CAPTCHAs, or blocked flows are listed as blockers in the report. It does not execute load, performance, or penetration testing.