dogfood

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill dogfood-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/software-development/dogfood
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill dogfood-vivekgoquest

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. This Skill systematizes the process by driving a browser toolset through a five-phase workflow that finds, classifies, and documents bugs with evidence. ## Core Features & Use Cases - Systematic Exploration: Navigates pages, clicks elements, fills forms, and checks the JS console after every interaction to surface hidden errors. - Evidence Collection: Captures annotated screenshots for every issue and classifies findings using a severity/category taxonomy (Critical to Low; Functional, Visual, Accessibility, Console, UX, Content). - Structured Reporting: Produces a deduplicated, severity-sorted bug report with an executive summary, reproduction steps, and a summary table. - Use Case: Point it at a staging URL before a release and receive a report.md with screenshots documenting a broken checkout button, console exceptions on the login page, and missing alt text on product images. ## Quick Start Dogfood the web app at https://staging.example.com with full-site scope 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 app?▼

Provide a target URL and testing scope, then the Skill navigates pages, interacts with buttons and forms, checks the JavaScript console after each action, and captures screenshots of issues. It finishes by generating a severity-sorted bug report with reproduction steps.

What browser tools are needed for web app bug testing?▼

The workflow requires a browser toolset including browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. These cover navigation, DOM inspection, interaction, screenshots, and console error detection.

How are bugs classified in a QA report?▼

Issues are assigned a severity (Critical, High, Medium, Low) and a category (Functional, Visual, Accessibility, Console, UX, Content) using the taxonomy in references/issue-taxonomy.md. Duplicates are merged and the final report is sorted by severity.

Can this test form validation and edge cases?▼

Yes, the workflow explicitly tests forms with both valid and invalid inputs, empty submissions, keyboard navigation, and edge cases like long text, special characters, and rapid clicking. Console output is checked after every significant interaction.

What are the limitations of automated exploratory testing?▼

It depends on the availability of the browser toolset and cannot execute areas blocked by authentication or missing credentials, which are recorded as blockers in the report. Responsive testing is limited to issues visible in captured screenshots rather than multi-device emulation.