dogfood

Run structured exploratory QA testing on web applications with reproducible bug evidence.

3|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/DarkArty07/Aether-Agents --skill dogfood-darkarty07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/DarkArty07/Aether-Agents/tree/main/home/skills/dogfood
Command: npx skills add https://github.com/DarkArty07/Aether-Agents --skill dogfood-darkarty07

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of unstructured, inconsistent web application QA testing that misses critical bugs, lacks reproducible evidence, and produces unactionable reports.

Core Features & Use Cases

  • 5-Phase Systematic Workflow: Structured plan, explore, evidence collection, categorization, and reporting process to ensure comprehensive test coverage.
  • Automated Evidence Capture: Integrates with browser tooling to collect screenshots, console errors, and interaction logs for every identified issue.
  • Standardized Bug Classification: Uses a built-in issue taxonomy to assign severity and category to all findings for clear prioritization.
  • Use Case: For example, use this Skill to test a new e-commerce checkout flow, catching broken buttons, form validation errors, and JavaScript console issues before public launch.

Quick Start

Use the dogfood skill to perform exploratory QA testing on your web app at https://your-app.com and generate a structured bug report with all evidence and severity classifications.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform systematic exploratory testing on a web app?

Exploratory web app testing applies a structured 5-phase workflow—plan, explore, collect evidence, categorize, and report—to ensure reproducible bug capture and comprehensive test coverage across interactive elements.

How do I generate structured bug reports with severity classification and screenshots?

Structured bug reporting captures screenshots, console errors, and step-by-step reproduction instructions, then applies an issue taxonomy to assign severity and category for clear prioritization.

Can I automate evidence collection like screenshots and console error detection during QA?

Yes, automated evidence collection integrates with native browser automation tooling to capture screenshots, JavaScript console errors, and interaction logs for every identified issue during testing.

What is the best way to test edge cases like empty states and error pages in a web application?

Edge case testing covers empty states, error pages, form validation, and navigation workflows by systematically exploring targeted scopes of the web app to identify broken interactive elements.

Does this QA approach work for both full-site and targeted scope testing of web apps?

Yes, this QA approach applies to both full-site and targeted scope testing, covering navigation, interactive elements, form validation, and JavaScript console error detection across the web app.

Why does unstructured exploratory testing fail to capture reproducible bug evidence?

Unstructured exploratory testing lacks a systematic workflow for evidence collection and issue classification, resulting in inconsistent reports that miss critical bugs and lack standardized severity prioritization.