dogfood

Explore web applications to discover bugs and generate structured QA reports.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/ChimeraFoundationa/Agentx --skill dogfood-chimerafoundationa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/ChimeraFoundationa/Agentx/tree/main/skills/dogfood
Command: npx skills add https://github.com/ChimeraFoundationa/Agentx --skill dogfood-chimerafoundationa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploration and QA testing of web applications using a browser toolset to identify bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

  • Systematic exploratory testing workflows across pages and features
  • Evidence capture with screenshots, console logs, and a final bug report
  • Structured bug reports following a standard taxonomy for issues and reporting

Quick Start

Run a browser-based QA session on your target site and generate a structured dogfood report of identified issues.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run exploratory QA testing on my web application?

Exploratory QA testing on web applications follows a 5-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. You navigate pages and flows, interact with features, check edge cases, and generate a structured bug report.

What is systematic browser-based bug discovery?

Systematic bug discovery is an exploratory testing process using a browser toolset to navigate web apps, trigger edge cases, capture evidence like screenshots and console logs, and classify issues using a defined taxonomy.

How are captured bugs categorized during web testing?

Captured bugs are categorized using a defined taxonomy during the Categorize phase. This structured classification ensures identified issues from browser testing sessions are organized consistently in the final report.

What evidence does browser QA testing collect for bug reports?

Browser QA testing collects evidence like screenshots and console logs during the Collect Evidence phase. This evidence supports the structured bug report generated after categorizing issues found across web application flows.

Can I use this for end-to-end testing across multiple web pages?

Yes, this applies to end-to-end testing of web apps, focusing on navigation and interaction across multiple pages and flows. It systematically explores features and edge cases to identify bugs throughout the application.