dogfood

Guide automated exploratory QA of web applications through a 5-phase workflow.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/DonZzzilla/kalshi-explorer --skill dogfood-donzzzilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/DonZzzilla/kalshi-explorer/tree/main/skills/user-skills/dogfood
Command: npx skills add https://github.com/DonZzzilla/kalshi-explorer --skill dogfood-donzzzilla

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?

Dogfood provides a systematic approach to QA testing for web applications, streamlining the process of identifying bugs, collecting evidence, and producing structured bug reports.

Core Features & Use Cases

  • Exploratory QA Testing: Systematic browser-based testing for finding issues in web apps.
  • Multi-Platform Compatibility: Runs on Linux, MacOS, and Windows.
  • Scalable Evidence Collection: Takes screenshots and logs for issue reproduction and tracking.
  • Automated Report Generation: Produces structured bug reports based on testing findings.
  • Use Case: Integrate into CI/CD pipelines to automate testing for new feature rollouts or ongoing QA for complex web applications.

Quick Start

To perform exploratory QA on the URL 'https://example.com' targeting specific areas, run 'dogfood url=https://example.com scope=special features output_dir=results'

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory QA testing for web applications?

Automated exploratory QA testing for web apps is guided through a 5-phase workflow: planning, exploration, evidence collection, categorization, and reporting. The process uses browser tools for navigation, snapshots, and element interactions to systematically identify bugs.

Can I run web app QA testing on Linux, MacOS, and Windows?

Yes, web app QA testing works across Linux, MacOS, and Windows. The automated browser testing process is compatible with all three operating systems, allowing you to perform systematic exploratory testing regardless of your platform.

How do I collect evidence and generate bug reports during browser testing?

Evidence collection during browser testing is handled by capturing screenshots and logging console outputs. These artifacts are gathered during the exploration phase and used to produce structured bug reports in the final reporting stage.

What is the best way to integrate exploratory QA into a CI/CD pipeline?

Integrating exploratory QA into a CI/CD pipeline is best achieved by running automated browser testing against new feature rollouts. The 5-phase workflow systematically uncovers issues and generates structured reports for ongoing web application validation.

Does browser-based QA testing support visual assessments and console logging?

Yes, browser-based QA testing supports visual assessments and console logging. The testing workflow utilizes browser vision capabilities to evaluate UI states and captures console logs to track errors during web application exploration.

How do I target specific features when testing a web app URL?

To target specific features when testing a web app URL, you define the scope parameter in the testing command. This directs the automated browser exploration to focus solely on the specified areas of the application.