qa-only

Name: qa-only
Availability: InStock
Author: hetsheth-droid

Explore web pages and interactions to generate a structured QA report.

Updated Mar 31, 2026

Search Tags:#automation #testing #screenshots #qa #web #bug-reporting

Ready to run

npx skills add https://github.com/hetsheth-droid/toolbox-template --skill qa-only-hetsheth-droid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/hetsheth-droid/toolbox-template/tree/main/incubating/gstack/qa-only
Command: npx skills add https://github.com/hetsheth-droid/toolbox-template --skill qa-only-hetsheth-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA bottlenecks slow down product quality. This Skill performs thorough automated testing of a web application to uncover bugs without modifying code or making changes to the environment.

Core Features & Use Cases

Systematic exploration of pages, interactions, and states to generate a reproducible defect report
Automated evidence collection including health scores, screenshots, and repro steps
Use Case: run on a feature branch to verify that new UI changes don't introduce obvious regressions while keeping code intact

Quick Start

Run the QA-only skill against your target URL to generate a structured, evidence-based QA 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 application QA testing to find bugs without modifying code?▼

Automated QA testing can explore pages, click elements, and collect a structured report without applying fixes. This approach generates reproducible findings, evidence-backed health scores, and screenshots across multiple pages and states while keeping your source code intact.

Can I run automated bug reporting against a feature branch to check for UI regressions?▼

Yes, automated bug reporting can run on a feature branch to verify that new UI changes don't introduce obvious regressions. It systematically explores interactions and states to generate a defect report, ensuring your deployment environment remains unchanged.

What do I need to provide to start automated QA testing of my web app?▼

To start automated QA testing, you need to provide a target URL or have a detected local app. The testing process uses this entry point to explore pages and collect evidence-backed health scores and screenshots.

Does automated QA testing support diff-aware testing for web applications?▼

Automated QA testing supports both diff-aware and full-mode testing for web applications. Diff-aware testing focuses on verifying specific changes, while full-mode testing performs a thorough exploration of all pages and states to generate a comprehensive report.

What is included in an automated QA defect report for a web application?▼

An automated QA defect report includes reproducible findings, evidence-backed health scores, screenshots, and repro steps. It systematically documents defects discovered while exploring pages, interactions, and states across the target web application.

When should I not use report-only automated QA testing?▼

You should not use report-only automated QA testing when you need to automatically fix bugs or modify source code. This approach is strictly designed for uncovering bugs and generating structured reports without making changes to the environment or deployment.