dogfood

Explore web applications to uncover bugs and document reproducible issues.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill dogfood-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/lgwanai/openforce/tree/main/skills/dogfood
Command: npx skills add https://github.com/lgwanai/openforce --skill dogfood-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents shipping buggy or confusing web experiences by turning ad-hoc testing into a repeatable exploratory QA session that produces actionable, evidence-backed findings.

Core Features & Use Cases

  • Systematic exploratory testing across pages, interactive controls, forms, and workflows to surface functional, UX, content, and console issues.
  • Repro-first issue documentation with step-by-step repro steps and captured evidence (annotated screenshots, and videos for interactive issues) suitable for handoff to responsible teams.
  • Session handling with optional authentication so you can test both public and signed-in experiences and capture auth state for reuse.

Quick Start

Tell the AI “dogfood vercel.com” and it will open the site, explore key flows, and generate a structured report with full reproduction evidence for every issue it finds.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform exploratory testing on my web app with reproducible evidence?

Exploratory testing for web apps involves systematically navigating pages, forms, and workflows to capture functional and UX issues. This approach generates reproducible findings with step-by-step instructions, annotated screenshots, and videos for interactive issues.

Can I test authenticated sessions during web QA testing?

Yes, web QA testing can handle optional authentication to evaluate signed-in experiences. The session captures the auth state for reuse, allowing you to systematically test both public and authenticated user flows within the same exploratory testing session.

What is the best way to document UX issues found during bug hunting?

The best way to document UX issues during bug hunting is a repro-first approach. It captures step-by-step reproduction instructions alongside annotated screenshots and videos for interactive problems, creating actionable evidence suitable for direct handoff to development teams.

How do I check for console errors while doing web testing?

Systematic web testing includes console error checks as part of its core coverage. As the agent-browser explores interactive controls and workflows across your application, it automatically captures console errors alongside functional and UX issues to produce a comprehensive quality report.

Does web testing work for complex form and workflow validation?

Yes, web testing systematically covers form and workflow validation. The agent-browser interacts with interactive controls across multiple pages, validating complex user journeys and capturing evidence of any functional failures or confusing UX issues encountered during the flows.

What are the limitations of automating exploratory testing for web apps?

Automating exploratory testing focuses on systematic coverage of navigation, forms, and console errors. However, highly subjective UX nuances or complex dynamic interactions may still require manual verification, as the automated agent prioritizes reproducible functional and workflow issues with captured evidence.