dogfood

Automates exploratory QA testing for web applications with structured bug reports.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill dogfood-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/Signmanal/VIGIL/tree/main/skills/dogfood
Command: npx skills add https://github.com/Signmanal/VIGIL --skill dogfood-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual web application quality assurance testing is often inconsistent, time-consuming, and misses subtle bugs, JavaScript console errors, and edge case issues that can slip into production and impact user experience.

Core Features & Use Cases

  • 5-Phase Systematic Workflow: Guides testers through planning, exploration, evidence collection, issue categorization, and report generation for full test coverage.
  • Browser Tool Integration: Leverages built-in browser tools to navigate pages, interact with elements, capture annotated screenshots, and monitor JavaScript console output for errors.
  • Standardized Issue Taxonomy: Classifies all found issues by severity (Critical to Low) and category (Functional, Visual, Accessibility, etc.) for clear prioritization.
  • Structured Bug Reporting: Generates shareable reports with executive summaries, per-issue details with evidence, and testing coverage notes.
  • Real-World Use Case: A security operations team testing a new internal incident response dashboard can use this skill to systematically explore all pages, catch broken navigation links, form validation errors, and uncaught JavaScript exceptions, then share a structured evidence-backed report with developers.

Quick Start

Use the dogfood skill to perform exploratory QA testing on the web app at https://your-target-app.com and produce a structured bug report with all collected evidence.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory QA testing for a web application?

You can automate exploratory QA testing by applying a 5-phase systematic workflow that covers planning, exploration, evidence collection, issue categorization, and report generation to eliminate manual testing inconsistencies and capture functional or visual bugs.

What is the best way to collect evidence and screenshots during web app testing?

The best way to collect evidence is by leveraging built-in browser tools to capture annotated screenshots and monitor JavaScript console output, which provides structured visual proof and logs for standardized bug reporting.

Can I classify bug severity and category for web application issues systematically?

Yes, bug issues can be classified systematically using a standardized taxonomy that assigns severity levels from Critical to Low and categories like Functional, Visual, and Accessibility, ensuring clear prioritization for development teams.

Does exploratory testing work for internal dashboards and browser-based tools?

Exploratory testing works effectively for internal dashboards and browser-based tools by systematically navigating pages to catch broken links, form validation errors, and uncaught JavaScript exceptions, then generating evidence-backed reports for developers.

How do I generate shareable bug reports with reproducible steps and visual proof?

You can generate shareable bug reports by compiling collected evidence and console logs into a structured document featuring an executive summary, per-issue details with visual proof, and testing coverage notes for clear developer handoff.