qa-only

Run report-only QA scans on web applications and generate structured health reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing accelerates defect discovery by producing structured reports that capture health scores, screenshots, and repro steps without performing fixes.

Core Features & Use Cases

  • Automated, non-intrusive QA scans that generate a health report with evidence.
  • Supports web applications across multiple pages and user flows, suitable for bug reporting or regression checks.
  • Use case: when stakeholders want a quick, thorough bug report without code changes, or when a formal QA pass is required before release.

Quick Start

Run a report-only QA scan on the target web app and generate a structured health report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a bug report with repro steps for a web application?

Performing report-only QA testing produces a structured health report that captures screenshots and repro steps for web applications during bug discovery or regression checks without applying any code fixes.

Can I run automated QA testing that only reports bugs and does not modify code?

Yes, you can run automated non-intrusive QA scans designed specifically to report bugs and document evidence without modifying code, ensuring the testing process remains strictly observational.

What is a health score in web testing and how does it help with regression checks?

A health score in web testing quantifies application stability during regression checks, providing stakeholders with a quick metric to assess overall quality based on structured QA evidence.

Do I need Bash or WebSearch to perform exploratory QA across multiple pages?

Yes, performing exploratory QA across multiple pages requires Bash, Read, Write, AskUserQuestion, and WebSearch to coordinate testing tasks, navigate flows, and present structured results.

When should I use a report-only QA approach instead of automated bug fixing?

Use a report-only QA approach instead of automated bug fixing when stakeholders want a quick, thorough bug report without code changes, or when a formal QA pass is required before release.