dogfood

Identify and report QA issues in web applications with screenshots and console logs.

2.8k|332|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/moltis-org/moltis --skill dogfood-moltis-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/moltis-org/moltis/tree/main/crates/skills/src/assets/dogfood
Command: npx skills add https://github.com/moltis-org/moltis --skill dogfood-moltis-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dogfood guides you through systematic exploratory QA testing of web applications to identify bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

  • Exploratory testing workflow: plan, explore, collect evidence, categorize, and report issues across a target web app.
  • Evidence collection: automatic screenshots, console capture, and traceable steps for reproducing bugs.
  • Structured reporting: produces a report with an issue taxonomy and recommended remediations for stakeholders.

Quick Start

Provide a target URL and testing scope, then start the dogfood QA workflow to automatically test the site and generate a comprehensive 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 testing for a web application?

Automated exploratory testing for a web application is guided through a systematic workflow that plans, explores, and collects evidence. It requires a target URL and testing scope to navigate, interact, and cover edge cases automatically.

Can I automatically capture screenshots and console logs during a QA session?

Yes, you can automatically capture screenshots and console logs during a QA session to gather evidence. The toolset records traceable steps for reproducing bugs alongside the captured web automation data.

What is the best way to generate a structured bug report with an issue taxonomy?

Generating a structured bug report with an issue taxonomy is achieved by running an exploratory QA workflow on a target web app. The process categorizes identified issues and outputs recommended remediations for stakeholders.

Do I need to provide a specific testing scope to start web QA?

Yes, you need to provide a target URL and a specific testing scope to start the web QA workflow. Defining the testing scope ensures the exploratory testing session covers the correct navigation and interaction paths.

How does systematic web QA handle edge-case coverage during end-to-end testing?

Systematic web QA handles edge-case coverage during end-to-end testing by applying a structured exploratory workflow. It targets navigation flows and interaction points across the web app to uncover bugs fast and collect supporting evidence.