dogfood

Guide systematic 5-phase exploratory QA testing of web applications and generate structured bug reports.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/shuff57/agent-evo --skill dogfood-shuff57
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/shuff57/agent-evo/tree/main/skills/.archive/dogfood
Command: npx skills add https://github.com/shuff57/agent-evo --skill dogfood-shuff57

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Dogfood Skill addresses the challenge of manually testing web applications, providing a systematic approach to identify bugs, evidence, and reports efficiently.

Core Features & Use Cases

  • Exploratory QA Testing: Guides systematic testing of web apps using browser toolset.
  • Bug Identification: Identifies and captures evidence of issues.
  • Structured Bug Reporting: Outputs structured bug reports for easy tracking.
  • Use Case: Test a web application for usability, functionality, and visual issues, automatically generating a comprehensive report.

Quick Start

Run 'dogfood test https://example.com --scope full-site' to start systematic QA testing of the full site.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory testing for a web application?

Automated exploratory testing uses a 5-phase workflow to navigate web applications, capture evidence of bugs, and generate structured reports. It requires a browser toolset to perform interactions like clicking, typing, and scrolling.

Can I generate structured bug reports automatically from QA testing?

Automated QA testing captures evidence of issues during execution and outputs structured bug reports. This provides a comprehensive tracking format for functionality, usability, and visual bugs found during the session.

What browser interactions are required for automated web testing?

Automated web testing requires browser toolset interactions including navigation, snapshot, click, type, vision, console, scroll, back, and press. These interactions enable systematic testing and evidence capture.

Does automated QA testing work for full-site scope or just single pages?

Automated QA testing supports full-site scope via commands like 'test --scope full-site'. This enables systematic exploration and bug identification across the entire web application, not just single pages.

What is the best way to capture visual and console errors during web testing?

The best way to capture visual and console errors is using browser toolset vision and console interactions during a 5-phase testing workflow. This systematically identifies issues and includes them in structured bug reports.