skills.rest
AtlasOmnia
AtlasOmniaCOMMUNITY
Explore all skills by this author →
Website𝕏@AtlasOmniaGitHub

dogfood

Tests web applications via browser automation and generates structured bug reports with screenshots.

115|9|Updated Aug 5, 2026
Search Tags:#screenshots#browser automation#web testing#bug report#console errors#exploratory testing#qa testing
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill dogfood-atlasomnia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/dogfood
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill dogfood-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual exploratory QA of web applications is slow and inconsistent, and bugs often go undocumented without screenshots, reproduction steps, or severity classification. ## Core Features & Use Cases - Systematic 5-Phase Workflow: Plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues by severity, and generate a final report. - Evidence Capture: Records console errors, annotated screenshots, and reproduction steps for every issue found. - Structured Reporting: Produces a report.md with an executive summary, per-issue severity tables, and testing coverage notes using a built-in template. - Use Case: Point the agent at a staging URL before a release; it navigates key flows, tests forms with valid and invalid inputs, checks the console for silent JS errors, and delivers a prioritized bug report. ## Quick Start Run exploratory QA testing on https://staging.example.com covering the signup and checkout flows and save the bug report to ./dogfood-output.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I run automated exploratory QA testing on a web app?▼

Provide a target URL, a testing scope, and an optional output directory. The agent follows a 5-phase workflow: plan a sitemap, explore pages with browser tools, collect screenshot evidence, categorize issues by severity, and generate a report.md file.

How to detect JavaScript console errors during browser testing?▼

Call browser_console after every navigation and significant interaction to capture silent JS errors. These errors are recorded per issue and included in the final bug report alongside screenshots and reproduction steps.

What browser tools are required for automated web QA testing?▼

The workflow requires the browser toolset: browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, and browser_press. Without these tools available, the testing phases cannot execute.

Can automated QA testing verify public visibility of pages?▼

Authenticated sessions can make restricted pages look public, so render success alone is unreliable. Verify the governing visibility setting directly, such as checking whether a Reddit wiki page allows anonymous access in its settings.

What are the limitations of automated exploratory browser testing?▼

Coverage depends on the planned sitemap, so untested areas are listed as out of scope in the report. Blockers like login walls or broken flows are documented, and responsive or edge-case issues require explicit scrolling and invalid-input testing.

Related Skills

Explore More Software Engineering Skills→
KarlinskySKarlinskyS

dogfood

Guide structured exploratory QA testing of web applications and generate bug reports.

Community
Advanced
TECH-HYTECH-HY

tpo-bug-tracking-template

Structures bug reports with severity classification, reproduction steps, and fix acceptance criteria.

Official
Basic
jfoxxjfoxx

testing-blocks

Guide AEM Edge Delivery Services testing with linting, browser validation, and unit tests.

Community
Intermediate
badhopebadhope

e2e-test

Automate end-to-end user flow testing across Playwright, Cypress, and Selenium.

Community
Advanced