dogfood

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

Updated May 29, 2026
One-click install
npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill dogfood-reimonsk8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Reimonsk8/hermes-9router-model-balancing/tree/main/scripts/skills/dogfood
Command: npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill dogfood-reimonsk8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual exploratory QA of web applications is slow and inconsistent, and bugs often go undocumented without screenshots, reproduction steps, or severity classification. This Skill systematizes browser-based testing so every issue is captured with evidence and reported in a consistent format. ## Core Features & Use Cases - Five-phase QA workflow: Plan, Explore, Collect Evidence, Categorize, and Report, using browser tools like navigate, snapshot, click, type, vision, and console inspection. - Structured issue taxonomy: Classifies findings by severity (Critical/High/Medium/Low) and category (Functional, Visual, Accessibility, Console, UX, Content) with deduplication. - Evidence-backed reporting: Generates a Markdown report with an executive summary, per-issue sections, screenshot references, console errors, and a summary table. - Use Case: Point it at a staging URL before a release; it navigates key flows, tests forms with valid and invalid inputs, captures JavaScript console errors, and produces a prioritized bug report. ## Quick Start Ask the agent to dogfood-test your web app at a given URL with a defined scope and save the bug report and screenshots to an output directory.

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, then the skill follows a five-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues by severity, and generate a structured Markdown report.

How are bugs classified in a QA report?▼

Issues are classified by severity (Critical, High, Medium, Low) and category (Functional, Visual, Accessibility, Console, UX, Content) using the taxonomy in references/issue-taxonomy.md, then deduplicated and sorted by severity.

What browser tools are required for web app testing with this skill?▼

The skill requires a browser toolset including browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press to interact with and inspect pages.

Can automated QA detect JavaScript console errors?▼

Yes, the workflow checks browser_console after every navigation and significant interaction to catch uncaught exceptions, failed network requests, and deprecation warnings that are invisible in the rendered page.

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

It depends on the available browser toolset and cannot execute code-level unit tests or load testing. Areas behind authentication or blocked by site errors are documented as untested blockers in the report.