dogfood

Identify and document web application issues through structured exploratory QA.

78|16|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill dogfood-sheawinkler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/sheawinkler/hermes-agent-ultra/tree/main/skills/dogfood
Command: npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill dogfood-sheawinkler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploratory QA of web apps to uncover bugs, evidence, and actionable reports.

Core Features & Use Cases

  • Guided exploratory testing across browser tools to surface issues quickly.
  • Capture evidence (screenshots, console logs) and generate structured bug reports.
  • Reproducible workflow for scoped testing and fast triage.

Quick Start

Provide a target URL and testing scope to begin an exploratory QA session 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 perform exploratory testing on a web application to find bugs?

Exploratory testing of web applications involves navigating targeted scopes to identify issues, capturing evidence like screenshots and console logs, and generating reproducible bug reports for fast triage.

How do I generate a structured bug report from a web testing session?

Generate a structured bug report by capturing screenshots and console logs during browser testing, then compiling findings into a standardized report with reproducible steps and an executive summary.

What do I need to start a browser QA session for a specific URL?

To start browser QA, you need browser tool access, a target URL, and a defined testing scope to guide the exploratory session and produce standardized bug reports.

Can I capture console logs and screenshots during exploratory web testing?

Yes, during exploratory web testing you can capture console logs and screenshots as evidence to document identified issues and support reproducible bug reports.

What is the best way to document issues found during web app dogfooding?

The best way to document issues during web app dogfooding is applying structured exploratory QA to capture screenshots, console logs, and a reproducible bug report for each finding.

Why does my exploratory QA workflow lack reproducible bug reports?

Your exploratory QA workflow lacks reproducible bug reports if it fails to capture evidence like screenshots and console logs within a structured testing scope for accurate issue triage.