dogfood

Explore web applications and generate structured bug reports with reproduction evidence.

14|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/syedsaif666/LGTM --skill dogfood-syedsaif666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/syedsaif666/LGTM/tree/main/skills/dogfood
Command: npx skills add https://github.com/syedsaif666/LGTM --skill dogfood-syedsaif666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual web application testing often misses critical bugs, and findings lack the reproducible evidence engineering teams need to quickly triage and fix issues, leading to delayed releases and unresolved user-facing problems.

Core Features & Use Cases

  • Systematic Exploratory Testing: Follows a structured workflow to explore all core app features, navigation paths, and edge cases, covering visual, functional, UX, content, performance, console, and accessibility issue types.
  • Full Reproduction Evidence: Generates structured bug reports with step-by-step screenshots, repro videos, and detailed reproduction steps for every finding, so issues can be handed directly to responsible teams with no follow-up work needed.
  • Use Case: For example, if you are preparing a new SaaS dashboard for launch, use this skill to run a full exploratory QA session and get a shareable report of all bugs with exact reproduction steps your dev team can act on immediately.

Quick Start

Use the dogfood skill to run a full exploratory QA test on the web app at https://app.example.com and generate a structured bug report with full reproduction evidence for all issues found.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory testing for a web application?

Automated exploratory testing systematically explores web applications to identify bugs and UX issues. It applies structured workflows to cover functional, visual, and accessibility edge cases, producing structured bug reports with step-by-step screenshots and reproduction videos for engineering teams.

How do I generate bug reports with reproduction evidence for my QA team?

Generating bug reports with reproduction evidence requires systematically exploring web apps to capture detailed reproduction steps, screenshots, and videos. This process yields structured reports that engineering teams can directly triage without needing follow-up clarification.

Can I run QA automation testing on internal SaaS tools before launch?

Yes, QA automation testing can be applied to any public or internal web platform, including SaaS dashboards and internal tools. It runs full exploratory QA sessions to identify bugs and generate shareable reports with exact reproduction steps for immediate developer action.

What is the best way to find web app bugs with reproducible steps?

The best way to find web app bugs with reproducible steps is through systematic exploratory testing that covers navigation paths and edge cases. This approach captures visual, functional, and performance defects, outputting structured reports with detailed reproduction steps and evidence.

What types of defects can exploratory testing identify in web applications?

Exploratory testing identifies visual, functional, UX, content, performance, console, and accessibility defects in web applications. It systematically explores core features and navigation paths to uncover these issue types, generating reports with full reproduction evidence for each finding.

Why does manual web testing often result in unresolved bugs?

Manual web testing often misses critical bugs and lacks the reproducible evidence engineering teams need to quickly triage and fix issues. Without step-by-step screenshots and reproduction videos, findings are delayed, leading to unresolved user-facing problems and postponed releases.