dogfood

Automate browser-based exploratory QA testing with evidence and bug reports.

6|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Strategic-Automation/arachne --skill dogfood-strategic-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Strategic-Automation/arachne/tree/main/src/arachne/skills/default/dogfood
Command: npx skills add https://github.com/Strategic-Automation/arachne --skill dogfood-strategic-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA testing is tedious and error-prone; this skill provides a repeatable, evidence-driven approach to exploring web apps, documenting issues, and delivering structured reports.

Core Features & Use Cases

  • Systematic 5-phase QA workflow (Plan, Explore, Collect Evidence, Categorize, Report)
  • Browser tool integration to navigate, snapshot, test inputs, and capture evidence
  • Automatic issue documentation with evidence and taxonomy classification using references/issue-taxonomy
  • Generates a consolidated QA report at the end of the workflow for audits and handoffs

Quick Start

Describe a target URL and scope, then run the dogfood QA workflow to generate a structured report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How does automated browser QA testing capture evidence for bug reports?

Automated browser QA testing captures evidence by navigating web apps, taking screenshots, recording console logs, and classifying issues into a taxonomy to generate structured, reproducible bug reports.

What is the best way to structure exploratory testing for web applications?

The best way to structure exploratory testing is using a systematic five-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report, ensuring a repeatable and evidence-driven audit trail.

How do I generate a consolidated QA report from an exploratory testing session?

You generate a consolidated QA report by running an automated workflow that documents discovered issues, attaches captured browser evidence, classifies them by taxonomy, and outputs a final handoff-ready audit document.

Can I use automated browser testing for ad-hoc URL scope testing without setup?

Yes, you can perform ad-hoc URL scope testing by defining a target URL and testing scope, which triggers the automated QA workflow to explore inputs, capture evidence, and categorize issues without requiring external dependencies.

Does automated exploratory QA testing replace manual test case creation?

Automated exploratory QA testing complements manual test case creation by focusing on systematic discovery, evidence collection, and issue taxonomy classification rather than executing predefined deterministic test scripts.

Why are console logs and screenshots important in automated bug reporting?

Console logs and screenshots are important in automated bug reporting because they provide objective, reproducible evidence that validates discovered issues and ensures a reliable audit trail for developer handoffs.