qa-only

Automate web app QA testing and generate evidence-rich bug reports.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/lachieh/babytalk --skill qa-only-lachieh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/lachieh/babytalk/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/lachieh/babytalk --skill qa-only-lachieh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables thorough QA testing of web applications by generating structured bug reports with evidence, health scores, and reproducible steps, without applying any fixes.

Core Features & Use Cases

  • Automated browser QA pass that navigates the app, validates UI state, checks forms, and captures console errors.
  • Evidence-rich reporting that includes health scores, screenshots, and reproducible steps for each issue.
  • Use Case: When stakeholders want a complete bug report without code changes, to triage issues and inform fixes.

Quick Start

Initiate a browser QA run on your target app and generate a detailed, evidence-backed bug report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate web QA testing to generate bug reports without modifying code?

Automated web QA testing generates structured bug reports with health scores, screenshots, and reproducible steps without applying any code fixes. It navigates your application to validate UI state, verify forms, and capture console errors for stakeholders to triage.

What is a health score in web application QA reporting?

A health score in QA reporting quantifies the overall stability of a web application based on automated test results. It aggregates UI validations, form checks, and console error captures into a deterministic metric for stakeholders.

Can I capture console errors and screenshots during automated browser testing?

Yes, automated browser QA testing captures console errors and screenshots as evidence during navigation. It requires a browser automation capability to attach visual proof and console logs to structured bug reports.

Do I need a deterministic test plan for web application QA testing?

Yes, a deterministic test plan is required to execute web application QA testing and generate consistent health scores. It ensures reproducible steps and structured bug reports are reliably generated across runs.

Why use a QA-only approach instead of automated testing that applies fixes?

A QA-only approach separates verification from code changes, delivering evidence-rich reports for triage without altering the codebase. It is ideal when stakeholders need to review issues and inform fixes independently.