skills.rest
kaminocorp
kaminocorpOFFICIAL
Explore all skills by this author →
Website𝕏@kaminocorpoGitHub

dogfood

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

228|35|Updated Mar 9, 2026
Search Tags:#automation#qa#web-testing#browser#bug-reporting#exploratory-testing
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha --skill dogfood-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/kaminocorp/hermes-alpha/tree/main/hermes-agent/skills/dogfood
Command: npx skills add https://github.com/kaminocorp/hermes-alpha --skill dogfood-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA guidance to perform exploratory browser-based testing, capture evidence, and generate structured reports for web applications.

Core Features & Use Cases

  • Phase-based workflow (Plan, Explore, Collect Evidence, Categorize, Report) to organize and repeat testing efficiently.
  • Browser toolset integration to navigate pages, capture screenshots, inspect console logs, and compile evidence.
  • Output-ready bug reports that help developers reproduce issues and QA teams communicate findings.

Quick Start

Provide a target URL and testing scope to start a browser-based QA session.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory web testing to uncover bugs?▼

To automate exploratory web testing, you provide a target URL and testing scope to trigger a 5-phase workflow: Plan, Explore, Collect Evidence, Categorize, and Report. This process systematically navigates pages, captures evidence, and outputs a structured bug report.

What's the best way to generate structured bug reports from browser-based QA?▼

Generating structured bug reports from browser-based QA involves navigating typical user flows like forms and dynamic interactions to capture screenshots and console logs. This systematic evidence collection helps developers quickly reproduce and fix identified issues.

Do I need a specific browser toolset to perform systematic QA testing?▼

Yes, systematic QA testing requires a browser toolset to navigate pages, capture screenshots, and inspect console logs. This toolset integration is necessary to collect the evidence needed for comprehensive web application bug reporting.

How does systematic exploratory testing handle dynamic interactions and forms?▼

Systematic exploratory testing handles dynamic interactions and forms by applying a structured phase-based workflow. It navigates these specific user flows, captures evidence of any issues encountered, and categorizes them for the final report.

Can I define a specific testing scope for my web application QA sessions?▼

Yes, you define a specific testing scope alongside a target URL to start a browser-based QA session. This scope guides the exploratory testing process, ensuring the generated bug reports focus on your intended application areas.

Related Skills

Explore More Software Engineering Skills→
vikrant-projectvikrant-project
2

dogfood

Automate exploratory QA testing of web applications with browser toolset commands.

Community
Intermediate
cslsoftwarescslsoftwares

quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Community
Intermediate
Jesse-L-MJesse-L-M

browse

Automate browser-based QA testing with scripted interactions and screenshot diffing.

Community
Advanced
DIGI-UWDIGI-UW

openelis-test-catalog-qa

Automate browser-based QA testing for OpenELIS Global with Playwright and generate pass/fail reports.

Official
Advanced