dogfood

Explore web applications and report bugs with screenshots and console evidence.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill dogfood-sethypagna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/dogfood
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill dogfood-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you perform structured exploratory QA on web applications so you can uncover bugs, capture evidence, and produce clear reports without losing track of what was tested.

Core Features & Use Cases

  • Systematic Exploration: Navigate pages, inspect the interface, and test interactive elements in a repeatable QA workflow.
  • Evidence Collection: Capture screenshots, console errors, and reproduction details for each issue you find.
  • Reporting Output: Turn findings into a severity-ranked bug report with summaries, steps to reproduce, and testing coverage notes.
  • Use Case: Use this Skill when you need a fast but thorough review of a staging site, a new feature release, or a suspected regression before shipping.

Quick Start

Give the Skill a target URL, the testing scope, and an optional output directory so it can explore the site and generate a structured QA 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 QA testing on a web app to systematically find bugs?▼

Exploratory QA testing involves systematically navigating landing pages, testing forms, and edge cases while capturing screenshots and console errors. You can scope a test to a full site or a specific feature release to structure your bug hunting.

What's the best way to capture evidence and report bugs found during web app testing?▼

Bug reporting requires capturing browser snapshots, console checks, and visual annotations for each issue. These findings are then compiled into a structured, severity-ranked report with summaries, reproduction steps, and testing coverage notes.

Can I scope browser automation testing to just a single navigation flow instead of the full site?▼

Yes, you can scope browser automation testing to either a full-site review or a targeted area like a specific navigation flow. This ensures fast, thorough reviews of staging sites or suspected regressions before shipping.

Do I need to provide a target URL to start testing web apps for responsive behavior and edge cases?▼

Yes, you need to provide a target URL and the testing scope to start testing web apps. An optional output directory can also be specified so the tool can explore the site and generate a structured QA report.

Does exploratory testing cover responsive behavior and console errors across different page flows?▼

Yes, exploratory testing covers responsive behavior and console checks across landing pages, navigation flows, and forms. It systematically captures these errors alongside visual annotations to document edge cases found during the review.