dogfood

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

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

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 and produces a complete, evidence-backed bug report. ## 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: Classify every finding by severity (Critical/High/Medium/Low) and category (Functional, Visual, Accessibility, Console, UX, Content) using a built-in reference taxonomy. - Console Error Detection: Capture silent JavaScript errors after every navigation and interaction, surfacing high-value defects that visual inspection misses. - Use Case: Point the Skill at a staging URL before a release; it navigates key user flows, tests forms with valid and invalid inputs, captures annotated screenshots of defects, and outputs a report.md with an executive summary and per-issue reproduction steps. ## Quick Start Run exploratory QA testing on https://staging.myapp.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 app?▼

Provide a target URL and testing scope, then follow the 5-phase workflow: plan a sitemap, explore pages with browser navigation and snapshots, collect screenshot evidence of issues, categorize findings by severity, and generate a structured report.md.

How to find JavaScript errors while testing a website?▼

Check the browser console after every navigation and significant interaction using the browser_console tool. Silent uncaught exceptions and failed network requests are high-value findings that visual inspection alone will miss.

What should a QA bug report include?▼

A bug report should include an executive summary with severity counts, per-issue sections with reproduction steps, expected versus actual behavior, screenshot evidence, console errors, and a summary table. The included report template covers all of these sections.

How are bugs classified by severity in QA testing?▼

Issues are classified as Critical, High, Medium, or Low based on impact: Critical breaks core functionality or loses data, High significantly impairs features, Medium affects experience without blocking, and Low covers polish issues. Categories include Functional, Visual, Accessibility, Console, UX, and Content.

What are the limitations of automated exploratory browser testing?▼

It depends on the availability of browser automation tools and cannot replace deep load testing, security penetration testing, or assistive-technology audits. Areas behind authentication or payment walls may become blockers that are documented in the report's coverage section.