dogfood

Execute exploratory QA testing of web applications with navigation, interaction, and screenshot capture.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/lxh755818-bot/obsidian-vault --skill dogfood-lxh755818-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/lxh755818-bot/obsidian-vault/tree/main/backup/skills/dogfood
Command: npx skills add https://github.com/lxh755818-bot/obsidian-vault --skill dogfood-lxh755818-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, browser_press, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps users systematically test web applications for bugs and collect evidence to produce structured bug reports, improving web app quality and user experience.

Core Features & Use Cases

  • Exploratory QA Testing: Navigate web applications, interact with elements, capture evidence, and generate structured bug reports.
  • Predefined Workflow: Follow a 5-phase systematic workflow to plan, explore, collect evidence, categorize, and report issues.
  • Customization: Customize the scope of testing, output directory, and include additional evidence and analysis as needed.

Quick Start

Use the dogfood skill to test the 'https://example.com' web app with a focus on 'navigation links' and save reports to './dogfood-output'.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I perform systematic exploratory QA testing on a web application?

Exploratory QA testing follows a 5-phase workflow to plan, explore, collect evidence, categorize, and report bugs. You navigate web applications, interact with elements, capture snapshots, and check console logs to generate structured bug reports.

How do I collect evidence for web testing bug reports?

To collect evidence for bug reporting, you execute browser interactions like navigation, clicking, and typing. The framework captures snapshots, console logs, and screenshots to document the exact state and errors of the web application.

Can I customize the scope of browser automation for QA testing?

Yes, you can customize the scope of browser automation QA testing. You can define specific testing targets like navigation links, set a custom output directory for reports, and include additional evidence and analysis as needed during the workflow.

What browser tools do I need for web testing and bug reporting?

Web testing and bug reporting require a browser toolset for navigation and interaction. Necessary capabilities include browser navigation, snapshots, clicking, typing, vision, console checking, scrolling, and pressing actions.

Are there limitations to using a predefined workflow for exploratory testing?

The predefined workflow structures exploratory testing into five phases, but its effectiveness depends on browser toolset availability. You must have browser navigation, interaction, and snapshot dependencies configured properly to execute the framework.