dogfood

Conducts structured exploratory web application testing and captures step-by-step bug reproduction evidence.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/coreyone/software-maestro --skill dogfood-coreyone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/coreyone/software-maestro/tree/main/quality/dogfood
Command: npx skills add https://github.com/coreyone/software-maestro --skill dogfood-coreyone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes references (resource) components.

What problem does it solve? Manual exploratory testing of web applications often produces vague bug reports that developers cannot reproduce. This Skill systematically explores a web app in a real browser, finds issues, and documents each one with video recordings, annotated screenshots, and numbered reproduction steps so every finding is provable. ## Core Features & Use Cases - Systematic Exploration: Walks through navigation, forms, interactive elements, edge cases, and console errors using the agent-browser CLI with a named session. - Repro-First Documentation: Records videos and step-by-step screenshots for interactive bugs, and single annotated screenshots for static issues like typos or misalignment. - Structured Reporting: Generates a severity-categorized report (critical/high/medium/low) from a template, with an issue taxonomy reference covering visual, functional, UX, content, performance, console, and accessibility categories. - Use Case: Point it at a staging deployment before a release. It signs in if needed, explores core workflows like a real user, and delivers a report of 5-10 well-documented issues with full reproduction evidence. ## Quick Start Dogfood https://staging.myapp.com and produce a bug report with reproduction videos for every issue you find.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run an exploratory testing session on a web app?▼

Provide the target URL, such as "dogfood vercel.com", and the session starts immediately with sensible defaults. It explores the app systematically, tests interactive elements, and documents each issue with reproduction evidence in a structured report.

How do I document a bug with reproduction steps and video evidence?▼

For interactive bugs, the session records a repro video before reproducing, takes a screenshot at each step, and captures an annotated screenshot of the broken state. Static issues like typos only need a single annotated screenshot.

Does the dogfood testing workflow support authenticated pages?▼

Yes, it can sign in with provided credentials by filling login forms through the browser session, and it saves the authentication state to a JSON file for reuse. For OTP or email codes, it pauses and asks the user for the code.

What types of issues does exploratory web testing look for?▼

The issue taxonomy covers seven categories: visual, functional, UX, content, performance, console errors, and accessibility. Each issue is rated critical, high, medium, or low based on whether it blocks workflows or is cosmetic.

Why use agent-browser directly instead of npx agent-browser?▼

The direct agent-browser binary uses the fast Rust client, while npx routes through Node.js and is significantly slower. All session commands should invoke the binary directly for better performance.