dogfood

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Junkfooooood/hermes-governance --skill dogfood-junkfooooood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Junkfooooood/hermes-governance/tree/main/skills/dogfood
Command: npx skills add https://github.com/Junkfooooood/hermes-governance --skill dogfood-junkfooooood

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 ship without documented evidence. This Skill automates systematic browser-based testing, captures screenshots and console errors as evidence, and produces a structured bug report. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Plan, explore, collect evidence, categorize, and report — covering navigation, forms, interactive elements, and edge cases across the target site. - Evidence Collection: Captures annotated screenshots, console errors, and reproduction steps for every issue found. - Standardized Issue Classification: Uses a severity (Critical/High/Medium/Low) and category (Functional/Visual/Accessibility/Console/UX/Content) taxonomy to deduplicate and prioritize findings. - Use Case: Point the Skill at a staging URL before a release; it navigates key user flows, tests forms with valid and invalid inputs, checks the console for silent JavaScript errors, and delivers a report.md with severity-ranked issues and screenshot evidence. ## Quick Start Run exploratory QA testing on https://staging.example.com covering the signup and checkout flows and save the bug 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 follow the 5-phase workflow: plan a sitemap, explore pages with browser navigation and interaction, collect screenshot and console evidence, categorize issues by severity, and generate a structured report.

How to find JavaScript errors while testing a website?

Check the browser console after every navigation and significant interaction using browser_console. Silent uncaught exceptions, failed network requests, and unhandled promise rejections are high-value findings classified under the Console category.

What browser tools does this QA testing workflow require?

It requires a browser toolset with browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. Without these tools the exploration and evidence collection phases cannot run.

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. Issues are deduplicated and sorted Critical-first in the final report.

What are the limitations of automated exploratory browser testing?

It only covers pages and flows reachable through the browser toolset, so areas behind unavailable credentials or blocked by blockers are listed as untested in the report. It does not replace load testing, security penetration testing, or formal accessibility audits.