dogfood

Automate exploratory QA testing of web applications with browser tools and generate evidence-rich bug reports.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill dogfood-cloudliness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11/tree/main/skills/dogfood
Command: npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill dogfood-cloudliness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA testing of web applications by guiding exploratory browser interactions, capturing evidence, and generating structured reports.

Core Features & Use Cases

  • Guided browser exploration to identify defects across pages and flows.
  • Evidence collection through screenshots, console logs, and annotated notes.
  • Structured bug reporting with a ready-to-use template and taxonomy.

Quick Start

Initiate a browser-based QA session on a target URL, describe the testing scope, and generate a comprehensive dogfood report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory web QA testing to find bugs?

Automated exploratory web QA testing uses browser automation tools to systematically navigate target URLs, detect defects, and generate structured reports with screenshots and console logs.

What is the best way to generate evidence-rich bug reports during browser testing?

Evidence-rich bug reports are generated by capturing screenshots, console logs, and annotated notes during systematic browser interactions, which are then compiled into a structured, taxonomy-aligned issue list.

How do I perform systematic regression checks across defined target URLs?

Systematic regression checks are performed by initiating a browser-based QA session, defining the testing scope and target URLs, and applying exploratory interactions to detect defects and edge cases.

Does automated QA testing work for accessibility and edge case detection?

Automated QA testing applies to accessibility considerations and edge case detection by guiding exploratory browser interactions across defined scopes to identify and document defects comprehensively.

What do I need to run a multi-phase QA report for web applications?

Running a multi-phase QA report requires a browser toolset, a target URL, and a clearly described testing scope to output structured findings containing annotated evidence and a taxonomy-aligned issue list.

Can I use this for manual QA campaigns as well as automated testing?

This approach applies to manual QA campaigns, regression checks, and exploratory testing by guiding browser interactions and capturing evidence to produce structured, multi-phase bug reports.