dogfood

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill dogfood-luckybbjason1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/dogfood
Command: npx skills add https://github.com/luckybbjason1/trading --skill dogfood-luckybbjason1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual exploratory QA of web applications is time-consuming and inconsistent, often missing silent JavaScript errors, broken flows, and visual defects that only surface through systematic interaction. ## Core Features & Use Cases - Systematic 5-Phase QA Workflow: Plan, explore, collect evidence, categorize, and report bugs across an entire web application using browser automation tools. - 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 triage findings. - Use Case: Point the agent at a staging URL before a release; it navigates pages, clicks elements, fills forms with valid and invalid inputs, checks the console, and produces a prioritized bug report with screenshot evidence. ## Quick Start Run exploratory QA testing on https://staging.example.com covering the signup and checkout flows and save the report to ./qa-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 the agent follows a 5-phase workflow: plan a sitemap, explore pages with browser navigation and interaction, collect screenshot evidence, categorize issues by severity, and generate a structured bug report.

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, failed network requests, and unhandled promise rejections are high-value findings classified under the Console category.

What types of bugs does browser-based QA testing detect?

It detects functional bugs like broken buttons and failed form submissions, visual issues like layout overlaps and broken images, accessibility problems, console errors, UX gaps like missing feedback, and content issues like typos or placeholder text.

Does this QA workflow require any browser automation tools?

Yes, it requires a browser toolset providing browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. Without these tools the testing workflow cannot execute.

What are the limitations of automated exploratory web testing?

It only covers pages and flows reachable through the browser session, so authenticated areas without credentials, payment transactions, and backend-only logic may be out of scope. Blocked areas are documented in the report's Testing Coverage section.