skills.rest
musical-basics
musical-basicsCOMMUNITY
Explore all skills by this author →
GitHub

dogfood

Conduct systematic exploratory QA testing of web applications with structured bug reports.

Updated Apr 11, 2026
Search Tags:#qa#web-testing#browser-automation#bug-report#exploratory-testing#issue-classification
One-click install
npx skills add https://github.com/musical-basics/hermes-build-2 --skill dogfood-musical-basics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/musical-basics/hermes-build-2/tree/main/skills/dogfood
Command: npx skills add https://github.com/musical-basics/hermes-build-2 --skill dogfood-musical-basics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a structured workflow for systematic exploratory QA testing of web applications, enabling detection of bugs, collection of evidence, and generation of comprehensive reports.

Core Features & Use Cases

  • 5‑phase systematic workflow leveraging browser navigation, snapshotting, console monitoring, and vision‑based annotation.
  • Automated issue classification using a predefined taxonomy and severity scoring.
  • Generation of a markdown report with executive summary, detailed issue sections, and embedded screenshots.

Quick Start

Ask the dogfood skill to test a website by providing its URL and testing scope.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory testing for a web application?▼

Automated exploratory testing of web applications is conducted through a 5-phase systematic workflow that orchestrates browser navigation, DOM inspection, console monitoring, and vision-based screenshot annotation to discover bugs and generate structured markdown reports.

What is the best way to classify and report bugs found during web testing?▼

Bug classification and reporting is handled by applying a predefined issue taxonomy with severity scoring, which outputs a markdown report containing an executive summary, detailed issue sections, and embedded annotated screenshots.

Can I capture console errors and DOM snapshots while testing a website?▼

Yes, console monitoring and DOM inspection are core features of the web testing workflow. The process orchestrates browser navigation while actively monitoring the console and inspecting the DOM to capture comprehensive testing evidence.

How do I generate a bug report with annotated screenshots from browser automation?▼

To generate a bug report with annotated screenshots, the browser automation workflow captures vision-based screenshot annotations during navigation, classifies the discovered issues, and compiles the evidence into a comprehensive markdown report.

Do I need to define a testing scope to run exploratory web QA?▼

Yes, a testing scope is required. To initiate exploratory web QA, you provide the target website URL alongside the testing scope, which directs the systematic 5-phase workflow toward comprehensive bug discovery.

What limitations exist when using systematic workflows for bug discovery?▼

Systematic bug discovery workflows are limited to web applications accessible via browser navigation and DOM inspection. The testing scope is confined to web sites requiring evidence capture, screenshot annotation, and structured markdown reporting.

Related Skills

Explore More Software Engineering Skills→
ldzhhxxldzhhxx
1

dogfood

Automate exploratory QA testing of web applications with browser automation.

Community
Advanced
ArabelaTsoArabelaTso
142

issue-report-generator

Generate structured Markdown issue reports from failing test cases.

Community
Intermediate
WillNigriWillNigri
33

qa-only

Identify web application defects and generate a structured QA report.

Community
Advanced
YangYuS8YangYuS8

playwright-cli

Automate browser testing workflows with Playwright via a CLI.

Community
Intermediate