Identify and document web application issues through guided exploratory QA testing.
npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill dogfood-monjyu1101
Please help me install this Agent Skill. Skill: dogfood Source: https://github.com/Monjyu1101/AiDiy2026/tree/main/backend_hermes/skills/dogfood Command: npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill dogfood-monjyu1101
It enables structured, exploratory QA testing of web applications using browser tooling to uncover issues, collect evidence, and generate a formal bug report.
Use cases: QA teams, product teams performing manual/automated-ish QA across web apps; capturing screenshots, logs.
Start a dogfood QA session by supplying a target URL and testing scope, then run the guided workflow.
High-intent search queries and answers about installing and using this skill.
Exploratory QA testing for web apps is executed through a guided 5-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. You start by supplying a target URL and testing scope to navigate, interact, and capture issues hands-on using a browser toolset.
The best way to collect evidence for a bug report is using a browser toolset to capture screenshots, analyze console logs, and record vision snapshots during interactivity testing. This generates actionable bug reports complete with a structured issue taxonomy.
Yes, you can use this guided QA workflow to test navigation and error handling on any web app. It applies to targeted test sessions requiring only a target URL and testing scope to systematically uncover and document application issues.
You need integrated browser tools to run an exploratory test session effectively. The workflow relies on these tools to navigate pages, click elements, type inputs, take snapshots, and analyze console outputs for comprehensive web app testing.
The systematic web app testing workflow involves five steps: planning the testing scope, exploring the application via browser tools, collecting evidence like screenshots and logs, categorizing discovered bugs, and reporting the final actionable results.
Limitations of exploratory QA include its focus on targeted test sessions rather than exhaustive automated regression. It requires a manually defined testing scope and relies on browser toolset availability, making it less suitable for continuous automated performance monitoring.
LamseyahEliasPerform exploratory QA testing of web applications and generate structured bug reports.
moltis-orgIdentify and report QA issues in web applications with screenshots and console logs.
BermudaLocalsIdentify and document browser-based QA issues with structured reports.
WillNigriIdentify web application defects and generate a structured QA report.
