dogfood

Identify and document browser-based QA issues with structured reports.

1|1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BermudaLocals/hermes-agent-lite --skill dogfood-bermudalocals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/BermudaLocals/hermes-agent-lite/tree/main/skills/dogfood
Command: npx skills add https://github.com/BermudaLocals/hermes-agent-lite --skill dogfood-bermudalocals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often struggle to systematically identify, document, and report browser-based defects across web applications. This skill provides a guided, repeatable workflow to explore, capture evidence, categorize issues, and generate structured reports to accelerate remediation.

Core Features & Use Cases

  • Structured exploratory testing workflow across web apps using a browser toolset.
  • Automated evidence capture including screenshots and console observations, and generation of a dogfood report.
  • Issue taxonomy-based categorization with severity and category, and a shareable executive summary.

Quick Start

Initiate a 5-minute exploratory QA pass on your target URL and generate a structured dogfood 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 and generate a bug report?

Exploratory testing on a web application involves systematically navigating the URL, capturing console observations and screenshots, categorizing browser-based defects by severity, and generating a structured dogfood report.

What is the best way to document browser-based QA issues during manual testing?

Documenting browser-based QA issues requires capturing evidence like screenshots and console logs during structured web exploration, then categorizing them by severity and taxonomy to produce a shareable executive summary.

Do I need a specific browser toolset to run regression checks on my web app?

Yes, regression checks require a browser toolset with navigate, snapshot, click, type, vision, console, and scroll capabilities to interact with web applications and capture evidence for the report.

Can I use automated evidence capture for manual QA workflows across a defined URL scope?

Yes, you can apply guided manual QA workflows across a defined URL scope to automate evidence capture, log categorized issues, and output a comprehensive report file to a specified directory.

What limitations exist when using structured exploration for browser QA testing?

Browser QA testing through structured exploration is limited to the defined URL scope and requires compatible browser toolsets; it cannot uncover defects outside the specified web application boundaries or without proper tool permissions.