Perform exploratory QA testing of web applications and generate structured bug reports.
npx skills add https://github.com/afel6/scal-ai-pipeline --skill dogfood-afel6
Please help me install this Agent Skill. Skill: dogfood Source: https://github.com/afel6/scal-ai-pipeline/tree/main/hermes_skills_library/dogfood Command: npx skills add https://github.com/afel6/scal-ai-pipeline --skill dogfood-afel6
This skill eliminates inconsistent, ad-hoc exploratory testing by providing a repeatable, evidence-driven workflow that finds, reproduces, and documents web application defects so teams can prioritize and fix them efficiently.
Run an exploratory QA session against https://example.com focusing on login, search, and checkout flows and save all screenshots and the report to ./dogfood-output.
High-intent search queries and answers about installing and using this skill.
Systematic exploratory testing applies a structured 5-phase workflow—Plan, Explore, Collect Evidence, Categorize, and Report—to navigate web applications, identify bugs, and generate structured documentation of functional regressions and accessibility gaps.
Yes, automated bug report generation captures browser-driven evidence like annotated screenshots, DOM snapshots, and console logs, classifying issues by severity and category to produce an executive summary with per-issue sections for QA triage.
Running automated browser QA requires a browser toolset exposing navigation, snapshot, vision, click, type, console, scroll, back, and press commands to interact with web applications and output structured reports to a designated directory.
Testing end-to-end user journeys across responsive breakpoints is best handled through a repeatable, evidence-driven workflow that systematically navigates landing pages and form validations to surface critical defects before release.
Yes, exploratory QA testing detects accessibility checks and console errors by systematically navigating web application flows, capturing browser console output, and validating forms to document defects in a structured report.
You should avoid a structured exploratory testing workflow if your environment lacks a compatible browser toolset for navigation and snapshot capture, or if your project requires unit-level testing rather than end-to-end user journey documentation.
shuff57Guide systematic 5-phase exploratory QA testing of web applications and generate structured bug reports.
Eric-Pacheco95Generate Markdown release notes from merged pull requests, closed tickets, and commit history.
JamesFincherGuide exploratory web QA testing and generate evidence-backed bug reports.
johannesfritzRun pytest or Playwright/vitest suites and report pass/fail results.
