dogfood

Identify and report web application defects through systematic exploratory QA.

11|Updated May 17, 2026
One-click install
npx skills add https://github.com/StarryCod/cogitum --skill dogfood-starrycod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/StarryCod/cogitum/tree/main/cogitum/data/skills/dogfood
Command: npx skills add https://github.com/StarryCod/cogitum --skill dogfood-starrycod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web application QA is often manual, time-consuming, and scattered across disparate notes. This Skill provides a disciplined, repeatable workflow to systematically explore, capture evidence, and produce actionable bug reports.

Core Features & Use Cases

  • Plan, Explore, Collect Evidence, Categorize, and Report phases enable end-to-end bug discovery and documentation.
  • Utilizes browser toolset to navigate pages, interact with elements, capture screenshots, and classify issues using a taxonomy.
  • Use Case: run a full-site QA on a target URL and generate a structured report that includes URLs, steps to reproduce, and evidence artifacts.

Quick Start

Run a dogfood QA pass on a target URL and scope, then review the generated report.

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 a web application?

Exploratory testing for web apps involves navigating pages and interacting with elements to identify defects. This Skill applies a disciplined workflow to systematically explore targets, capture browser evidence like screenshots, and produce structured bug reports.

What's the best way to generate structured bug reports with evidence?

Generating structured bug reports requires capturing evidence and classifying issues using a taxonomy. This Skill outputs actionable reports that include target URLs, steps to reproduce, and evidence artifacts collected during the browser testing session.

Can I use browser tooling to run a full-site QA audit?

Yes, browser tooling can be used to run a full-site QA audit on a target URL. The Skill applies a structured workflow across single page apps and full-site scopes, utilizing browser tools to navigate, interact, and collect evidence.

How do I systematically categorize defects found during web testing?

Defects found during web testing can be systematically categorized using a predefined taxonomy. This Skill includes a categorization phase that classifies captured issues, ensuring the resulting bug reports are structured and actionable.

Do I need a browser toolset to capture QA evidence for single page apps?

Yes, a browser toolset is required to capture QA evidence for single page apps. The Skill depends on browser tooling to navigate elements, capture screenshots, and document the interactions needed to reproduce defects.

What phases are involved in systematic exploratory QA for web apps?

Systematic exploratory QA for web apps involves Plan, Explore, Collect Evidence, Categorize, and Report phases. This end-to-end workflow ensures disciplined bug discovery, evidence capture, and structured documentation across the testing target.