dogfood

Name: dogfood
Availability: InStock
Author: monjyu1101

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

1|Updated Jan 31, 2026

Search Tags:#testing #qa #evidence #browser #web #bug-report #exploratory

Ready to run

npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill dogfood-monjyu1101

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Monjyu1101/AiDiy2026/tree/main/backend_hermes/skills/dogfood
Command: npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill dogfood-monjyu1101

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables structured, exploratory QA testing of web applications using browser tooling to uncover issues, collect evidence, and generate a formal bug report.

Core Features & Use Cases

Systematic 5-phase QA workflow: Plan, Explore, Collect Evidence, Categorize, Report.
Hands-on browser-based testing with a suite of browser tools (navigate, click, type, snapshot, console, vision).
Generate actionable bug reports with evidence and taxonomy.

Use cases: QA teams, product teams performing manual/automated-ish QA across web apps; capturing screenshots, logs.

Quick Start

Start a dogfood QA session by supplying a target URL and testing scope, then run the guided workflow.

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?▼

Exploratory QA testing for web apps is executed through a guided 5-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. You start by supplying a target URL and testing scope to navigate, interact, and capture issues hands-on using a browser toolset.

What is the best way to collect evidence and generate a bug report for web UI issues?▼

The best way to collect evidence for a bug report is using a browser toolset to capture screenshots, analyze console logs, and record vision snapshots during interactivity testing. This generates actionable bug reports complete with a structured issue taxonomy.

Can I use this guided QA workflow to test navigation and error handling on any web app?▼

Yes, you can use this guided QA workflow to test navigation and error handling on any web app. It applies to targeted test sessions requiring only a target URL and testing scope to systematically uncover and document application issues.

Do I need specific browser tools to run an exploratory test session?▼

You need integrated browser tools to run an exploratory test session effectively. The workflow relies on these tools to navigate pages, click elements, type inputs, take snapshots, and analyze console outputs for comprehensive web app testing.

What steps are involved in the systematic web app testing workflow?▼

The systematic web app testing workflow involves five steps: planning the testing scope, exploring the application via browser tools, collecting evidence like screenshots and logs, categorizing discovered bugs, and reporting the final actionable results.

What are the limitations of exploratory QA for web applications?▼

Limitations of exploratory QA include its focus on targeted test sessions rather than exhaustive automated regression. It requires a manually defined testing scope and relies on browser toolset availability, making it less suitable for continuous automated performance monitoring.