dogfood

Test web applications for bugs and generate structured markdown QA reports.

Updated May 12, 2026
One-click install
npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill dogfood-hungthinh04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/hungthinh04/Hermes_AI_Agent/tree/main/skills/dogfood
Command: npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill dogfood-hungthinh04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically test web applications for bugs, broken flows, visual defects, accessibility problems, and console errors so you can produce clear QA evidence and reports.

Core Features & Use Cases

  • Exploratory browser testing: Navigate pages, inspect the DOM, click controls, type into forms, and exercise key user journeys.
  • Evidence collection: Capture screenshots, annotate visual issues, record console errors, and document reproducible steps.
  • Structured bug reporting: Classify findings by severity and category, de-duplicate related issues, and generate a polished markdown report.
  • Use Case: A tester can run a full-site review of a web app, identify regressions or broken interactions, and hand off a ready-to-share report with screenshots and reproduction steps.

Quick Start

Use the dogfood skill to test the target web app for bugs, capture evidence, and generate a structured QA 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 QA testing on a web application?

Exploratory web testing covers navigation, forms, interactive flows, edge cases, and responsive or accessibility issues. It requires capturing screenshots, checking console errors, documenting reproducible steps, classifying severity, and generating a structured markdown bug report.

What is the best way to document console errors and visual defects during browser testing?

Document console errors and visual defects by capturing screenshots, annotating visual issues, and recording console errors with reproducible steps. This evidence collection produces a structured markdown bug report classified by severity and category for clear QA handoff.

How do I generate a structured bug report for web testing findings?

Generate a structured bug report by classifying findings by severity and category, de-duplicating related issues, and compiling reproduction steps with screenshots. This yields a polished markdown report ready to share with developers for QA handoff.

Can I test responsive and accessibility issues during web application QA?

Yes, exploratory browser testing covers responsive and accessibility issues alongside navigation, forms, and interactive flows. It systematically exercises key user journeys to identify these problems and includes them in the structured bug report.

Does exploratory web testing work for finding broken user flows and regressions?

Yes, exploratory web testing works for finding broken user flows and regressions. By navigating pages, inspecting the DOM, and exercising key user journeys, testers identify broken interactions and regressions, then classify findings by severity in a markdown report.