dogfood

Executes systematic exploratory QA testing of web applications and generates structured bug reports.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill dogfood-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/dogfood
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill dogfood-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Dogfood QA reduces the chance of shipping broken web experiences by guiding structured exploratory testing that captures clear evidence for issues.

Core Features & Use Cases

  • Systematic exploratory testing: Plans what to test (pages, user flows, edge cases) and executes navigation and interactions in a disciplined way.
  • Evidence-first bug reporting: Uses snapshots, vision analysis, and console checks to collect reproducible details and screenshots.
  • Structured reporting output: Generates a complete report (executive summary, per-issue sections, and a summary table) suitable for sharing with developers.

Quick Start

Tell the agent the target URL, the scope to test (or “full site”), and the output directory you want, and it will produce a structured QA report with screenshot evidence.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform exploratory QA testing on a web application?

You can systematically execute web QA by navigating target URLs, inspecting the JavaScript console, capturing evidence screenshots, classifying issues, and generating a structured bug report with an executive summary and per-issue sections.

What is evidence-first bug reporting in web QA?

Evidence-first bug reporting captures reproducible details using snapshots, vision analysis, and console checks to document issues. It outputs a structured report with annotated visual element mapping and issue taxonomy suitable for sharing with developers.

Can I use this for regression checks on key user flows?

Yes, you can use this systematic exploratory testing approach for regression checks on key user flows. It fits scenarios like validating releases and investigating suspect pages across a defined target URL scope.

What's the best way to document JavaScript console errors during browser testing?

The best way to document console errors during browser testing is to inspect the JavaScript console alongside capturing snapshots and annotated visual element mapping, ensuring all issues are classified into a structured taxonomy with actionable evidence.

Does this web QA approach require specific browser testing dependencies?

No specific dependencies are required to use this approach. It relies on standard browser navigation, snapshot capture, and JavaScript console inspection to perform systematic exploratory testing and generate structured QA reports.

When should I not use exploratory testing for web applications?

You should avoid using exploratory testing for web applications when you need automated continuous integration checks, as this approach requires structured manual browser navigation and human-guided interactions to uncover bugs with actionable evidence.