dogfood

Identify and document web application bugs through guided exploratory QA testing.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill dogfood-changzhou-xj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/ChangZhou-xj/zxj_skill/tree/main/dogfood
Command: npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill dogfood-changzhou-xj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploratory QA of web applications can be time-consuming and inconsistent. This skill provides a structured, repeatable workflow to identify, capture evidence, and report issues across web interfaces.

Core Features & Use Cases

  • Browser-enabled exploration: navigate, interact, and collect evidence across pages.
  • Evidence generation: capture annotated screenshots and structured bug reports.
  • End-to-end workflow: plan, explore, collect, categorize, and document issues in a standardized format.

Quick Start

Provide a target URL and testing scope, then run the five-phase workflow to generate a structured bug report.

Frequently Asked Questions about dogfood

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

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

Systematic exploratory QA testing on a web application is executed through a guided workflow that navigates a target URL, interacts with elements, and generates a structured bug report. This approach standardizes how testers document discovered issues across web interfaces.

What is the best way to document bugs found during web browser exploration?

The best way to document bugs during web browser exploration is to use a structured workflow that automatically captures annotated screenshots as evidence. This ensures every reported issue includes standardized visual proof and categorized details.

Can I limit exploratory testing scope to specific areas of a target URL?

Yes, you can limit exploratory testing scope to specific areas of a target URL. The guided workflow supports defined scopes, allowing you to focus exploration on either a full site or designated sections before outputting the bug report.

How do I capture and annotate screenshots for web QA bug reports?

To capture and annotate screenshots for web QA bug reports, the testing workflow uses a browser toolset to interact with the application and collect evidence. These annotated screenshots are then compiled into a final structured report saved to a specified directory.

Does exploratory QA testing work without writing automated test scripts?

Yes, exploratory QA testing works without writing automated test scripts by following a deterministic workflow through a browser toolset. Testers navigate, snapshot, and interact with the application to manually identify and document bugs in a structured format.