dogfood

Automates exploratory QA of web apps with navigation and reporting.

539|39|Updated May 1, 2026
One-click install
npx skills add https://github.com/Tommy-yw/RunbookHermes --skill dogfood-tommy-yw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Tommy-yw/RunbookHermes/tree/main/skills/dogfood
Command: npx skills add https://github.com/Tommy-yw/RunbookHermes --skill dogfood-tommy-yw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, browser_press, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenges of web application QA testing by automating the process of bug detection, evidence collection, and report generation, significantly reducing manual effort and improving accuracy.

Core Features & Use Cases

  • Automated Bug Detection: Identifies issues in web applications through systematic testing.
  • Evidence Collection: Captures screenshots and console logs to document bugs.
  • Structured Reporting: Generates detailed reports with categorized issues and steps to reproduce.
  • Use Case: When testing a new feature release, use this Skill to automate the QA process, ensuring all critical paths are tested and any issues are quickly identified and reported.

Quick Start

Run the dogfood skill with the target URL, scope, and output directory: dogfood https://example.com --scope full-site --output ./dogfood-output

Frequently Asked Questions about dogfood

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate bug detection and evidence collection for web application testing?▼

Automated web application testing tools handle bug detection and evidence collection by performing systematic navigation and interaction, capturing screenshots and console logs to document identified issues. This approach reduces manual effort and improves accuracy.

How do I generate structured QA reports with steps to reproduce bugs?▼

Structured QA reports are generated by capturing evidence like screenshots and console logs during automated web testing, categorizing the discovered issues, and detailing the steps to reproduce them for effective issue tracking.

Do I need specific browser automation dependencies to run automated QA testing?▼

Yes, automated QA testing requires a browser toolset for navigation and interaction. Dependencies include tools for browser navigation, snapshot capture, clicking, typing, and console monitoring to execute the systematic exploratory testing process.

What is the best way to systematically test critical paths during a new feature release?▼

Systematically testing critical paths during a new feature release is best achieved through automated exploratory QA testing, which executes predefined navigations and interactions across the application scope to quickly identify and report issues.

Can I limit the scope of automated exploratory testing to a specific section of my web application?▼

Yes, you can limit the scope of automated exploratory testing by specifying a target URL and scope parameter. This directs the systematic navigation and interaction to focus testing efforts on a defined section or the full site.