dogfood

Automates exploratory QA testing of web applications with structured reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications to identify issues, collect evidence, and produce an actionable report.

Core Features & Use Cases

  • Phase-driven workflow (Plan, Explore, Collect Evidence, Categorize, Report) for targeted URLs.
  • Automatic evidence capture (screenshots, console logs, reproduction steps) to support issue triage.
  • Generates a comprehensive QA report with issue severity taxonomy for stakeholders.

Quick Start

Provide a target URL and testing scope, then run a complete dogfood QA pass to generate a structured 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?

You can automate exploratory QA testing by providing a target URL and testing scope to run a complete dogfood pass. This executes a phase-driven workflow covering planning, exploration, and evidence collection to produce a structured report.

What is systematic browser-based QA testing and how does it work?

Systematic browser-based QA testing automates web application exploration through a phase-driven workflow. It captures evidence like screenshots and console logs, categorizes issues using a severity taxonomy, and outputs a structured dogfood report.

Can I capture console logs and screenshots automatically during web testing?

Yes, automatic evidence capture collects screenshots, console logs, and reproduction steps during web testing. This evidence supports issue triage and is compiled into a comprehensive QA report for stakeholders.

How do I generate a bug report with issue severity taxonomy for stakeholders?

Generate a bug report with issue severity taxonomy by running an automated QA workflow that categorizes findings and collects evidence. The output is an executive dogfood report containing structured findings, screenshots, and console data.

Does this QA testing workflow require any specific testing frameworks or dependencies?

No specific testing frameworks or dependencies are required to run this QA testing workflow. It operates independently using a browser toolset to execute its phase-driven testing and evidence collection process.

What is the best way to structure issue categorization in automated web testing?

The best way to structure issue categorization is using a taxonomy-based classification system during automated web testing. This enforces consistent severity ranking and outputs structured findings within a comprehensive dogfood report.