claudegoodies
Skill

dogfood

From NousResearch

Exploratory QA of web apps: find bugs, evidence, reports.

Runs a 5-phase exploratory browser QA pass and produces a screenshot-backed bug report.

Use it when

  • Need a structured exploratory QA sweep of a web app before release
  • Want a bug report with severity/category tags and screenshot evidence
  • Checking for silent JS console errors across pages and interactions
  • Testing forms, navigation flows, and edge cases like 404s or empty states

Skip it if

  • Requires a browser toolset (browser_navigate, browser_snapshot, browser_vision, etc.) already available
  • No target URL or defined testing scope to give it
  • Need automated regression/unit testing rather than manual exploratory review

Facts

Repository
NousResearch/hermes-agent
Status
Actively maintained
Last commit
Source file
skills/dogfood/SKILL.md

Source preview

The instructions Claude Code reads when this skill runs.

# Dogfood: Systematic Web Application QA Testing

## Overview

This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.

## Prerequisites

- Browser toolset must be available (`browser_navigate`, `browser_snapshot`, `browser_click`, `browser_type`, `browser_vision`, `browser_console`, `browser_scroll`, `browser_back`, `browser_press`)
- A target URL and testing scope from the user

## Inputs

The user provides:
1. **Target URL** — the entry point for testing
2. **Scope** — what areas/features to focus on (or "full site" for comprehensive testing)
3. **Output directory** (optional) — where to save screenshots and the report (default: `./dogfood-output`)

## Workflow

Follow this 5-phase systematic workflow:

### Phase 1: Plan

1. Create the output directory structure:
   ```
   {output_dir}/
   ├── screenshots/       # Evidence screenshots
   └── report.md          # Final report (generated in Phase 5)
   ```
2. Identify the testing scope based on user input.
3. Build a rough sitemap by planning which pages and features to test:
   - Landing/home page
   - Navigation links (header, footer, sidebar)
   - Key user flows (sign up, login, search, checkout, etc.)
   - Forms and interactive elements
   - Edge
View full source on GitHub →

Other skills