qa-only

Generate structured QA reports with health scores, screenshots, and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables non-intrusive QA reporting by generating a structured bug report that includes a health score, evidence (screenshots, logs), and reproducible steps, without making any code changes.

Core Features & Use Cases

  • Systematic web application testing that produces a formal report with a health score and reproducible steps.
  • Evidence-rich reports including screenshots, console logs, and test artifacts to support bug verification.
  • Use cases include quick smoke checks, regression verification, or pre-release QA where documentation of issues is required rather than fixes.

Quick Start

Run /qa to start a QA pass and generate a structured 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 QA bug report with screenshots and reproducible steps for a web application?▼

You can generate a structured QA bug report with screenshots and reproducible steps for a web application by running a non-intrusive testing pass that documents issues without applying any code changes.

What is the best way to perform a pre-release smoke check with evidence like console logs and screenshots?▼

A pre-release smoke check with evidence like console logs and screenshots produces a formal report containing a health score and test artifacts, supporting bug verification without modifying your codebase.

Can I use this QA testing approach for regression verification without altering my source code?▼

Yes, you can use this QA testing approach for regression verification without altering your source code because it performs non-intrusive reporting and never applies fixes to the web application.

How do I document web application issues systematically into a standardized QA report?▼

To document web application issues systematically, the process generates a standardized QA report stored locally that includes a health score, evidence, and structured reproducible steps for fast bug reporting.

Do I need to provide repro steps manually when creating a bug report for a web application?▼

No, you do not need to provide repro steps manually when creating a bug report for a web application because the QA process automatically generates structured reproducible steps and captures evidence.

What limitations exist when using a report-only QA approach for web application testing?▼

The main limitation of this report-only QA approach for web application testing is that it strictly finds and documents issues but never applies fixes, requiring a separate process to resolve the bugs.