dogfood

Name: dogfood
Availability: InStock
Author: plaidmustache

Document bugs from exploratory QA of web applications with screenshots and structured reports.

Updated May 4, 2026

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

Ready to run

npx skills add https://github.com/Plaidmustache/hermes-nulab --skill dogfood-plaidmustache

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Plaidmustache/hermes-nulab/tree/main/skills/dogfood
Command: npx skills add https://github.com/Plaidmustache/hermes-nulab --skill dogfood-plaidmustache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploratory QA of web applications is often manual, time-consuming, and inconsistent. This skill provides a repeatable approach to discovering defects, collecting verifiable evidence, and delivering actionable reports.

Core Features & Use Cases

Systematic browser-based exploration across pages and user flows to reveal issues.
Evidence collection including annotated screenshots, console checks, and behavior notes.
Structured bug reporting that compiles findings into a report aligned with the dogfood template and issue taxonomy.

Quick Start

Navigate to the target web application, perform a focused exploratory QA pass, and 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 document bugs found during exploratory testing of web apps?▼

To document bugs found during exploratory testing of web apps, perform a focused browser-based QA pass. Capture verifiable evidence including annotated screenshots and console checks, then compile the findings into a structured bug report.

What is the best way to capture QA evidence during manual web app testing?▼

The best way to capture QA evidence during manual web app testing is to systematically explore user flows and collect verifiable proof. This includes generating annotated screenshots, recording console checks, and noting specific application behaviors.

Can I use a predefined template for structuring bug reports from browser-based QA?▼

Yes, you can use a predefined template for structuring bug reports from browser-based QA. The process aligns findings with a specific issue taxonomy and report template, ensuring defect discovery and evidence capture are consistently formatted.

Does exploratory QA work for identifying defects across complex user flows?▼

Yes, exploratory QA works for identifying defects across complex user flows. It applies systematic browser-based exploration across pages and user flows to reveal issues, focusing on defect discovery and structured reporting.

Why does structured bug reporting improve the consistency of web app QA?▼

Structured bug reporting improves web app QA consistency by replacing manual, time-consuming checks with a repeatable approach. It compiles evidence and defect discoveries into actionable reports aligned with a predefined taxonomy.

What limitations exist when using manual exploratory testing for web applications?▼

Limitations of manual exploratory testing for web applications include the time-consuming nature of the process and the potential for inconsistent defect discovery if not guided by a repeatable, structured reporting approach.