dogfood

Explore web applications through a 5-phase QA workflow and generate Markdown bug reports.

9|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill dogfood-cyapstaye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Cyapstaye/Adame_ver.open/tree/main/skills/dogfood
Command: npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill dogfood-cyapstaye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of inconsistent or incomplete manual testing by providing a structured, repeatable framework for exploratory QA that captures visual evidence and console errors.

Core Features & Use Cases

  • Systematic Exploration: Guides the agent through a 5-phase workflow including planning, navigation, interaction, evidence collection, and reporting.
  • Automated Reporting: Generates a comprehensive Markdown report including issue severity, reproduction steps, and annotated screenshots.
  • Use Case: Use this skill to perform a full regression test on a new deployment, ensuring that all interactive elements function correctly and no JavaScript errors are present in the browser console.

Quick Start

Initiate a full exploratory QA session on the target website by providing the URL and the desired testing scope to the agent.

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?

You can perform exploratory QA testing by using a structured 5-phase workflow that includes planning, exploration, evidence collection, categorization, and final report generation to identify functional, visual, and accessibility issues.

What is the best way to automate web application bug reporting with visual evidence?

Automated bug reporting with visual evidence is generated by capturing annotated screenshots and console errors during exploration, then compiling them into a comprehensive Markdown report with issue severity and reproduction steps.

Do I need browser toolset access for automated web testing and debugging?

Yes, you need browser toolset access for automated web testing and debugging, specifically requiring navigation, vision, console, and interaction capabilities to properly identify and capture JavaScript errors and functional defects.

Can I use this for regression testing on a new web deployment to check interactive elements?

Yes, you can use this for regression testing on a new web deployment to ensure all interactive elements function correctly and verify that no JavaScript errors are present in the browser console.

What types of web application issues does exploratory QA catch during navigation?

Exploratory QA catches functional, visual, and accessibility issues during navigation and interaction by systematically capturing both visual anomalies and console-based evidence throughout the testing session.