dogfood

Name: dogfood
Availability: InStock
Author: NossXBT

Guide automated exploratory testing of web applications and produce auditable bug reports.

13|3|Updated May 12, 2026

Search Tags:#automation #testing #qa #evidence #browser #web #bug-report

Ready to run

npx skills add https://github.com/kevinnft/ai-agent-skills --skill dogfood-kevinnft

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/dogfood
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill dogfood-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates systematic exploratory QA for web applications, enabling teams to discover bugs early by guiding testers through planning, exploration, evidence collection, and reporting.

Core Features & Use Cases

Guided 5-phase QA workflow (Plan, Explore, Collect Evidence, Categorize, Report)
End-to-end bug reporting with evidence (screenshots, console logs, step-by-step reproduction)
Works across single-page and multi-page apps and supports edge-case testing

Quick Start

Describe a target web application and instruct the agent to begin a structured QA session and generate a 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 QA testing for a web application?▼

Automated exploratory QA testing is guided through a 5-phase workflow covering planning, exploration, evidence collection, categorization, and reporting to systematically discover web app bugs.

What is the best way to generate an auditable bug report with screenshots and console logs?▼

An auditable bug report is generated by capturing screenshots, console logs, and step-by-step reproduction details during browser-based exploratory testing sessions.

Can I run structured QA testing on both single-page apps and multi-page sites?▼

Structured QA testing works across both single-page apps and multi-page sites, systematically covering navigation, forms, errors, and edge cases to identify issues.

How do you catch edge cases and navigation errors during web app testing?▼

Edge cases and navigation errors are caught by guiding automated browser tool interactions through a structured exploration phase that targets forms, errors, and unexpected application states.

Do I need specific browser automation dependencies to perform evidence collection?▼

No specific browser automation dependencies are required to perform evidence collection, as the testing workflow operates autonomously through internal browser tool interactions.