qa-only

Run report-only QA testing on web applications and generate health score reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

qa-only addresses the need for a thorough, report-only QA testing process for web applications. It generates detailed reports with health scores, screenshots, and repro steps without making any fixes.

Core Features & Use Cases

  • Report-Only Testing: Provides a systematic testing approach that focuses solely on reporting issues without altering the application.
  • Structured Reports: Outputs a report with a health score, screenshots, and repro steps for easy review.
  • Use Case: When required to perform QA testing that involves identifying and documenting bugs or issues without making corrections.

Quick Start

Use the /qa-only command to initiate report-only QA testing on your web application.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run report-only QA testing on a web application without fixing bugs?

Report-only QA testing on a web application is executed non-intrusively to generate a comprehensive report with a health score, screenshots, and repro steps without fixing issues. It is ideal for initial QA passes or when a separate team handles corrections.

What is a web application health score and how does it help with bug reporting?

A web application health score is a metric generated during report-only QA testing to quantify overall stability. It assists bug reporting by summarizing application quality alongside detailed repro steps and screenshots for easy review.

Do I need Bash and WebSearch tools to perform non-intrusive QA testing?

Bash, Read, Write, AskUserQuestion, and WebSearch tools are required to perform non-intrusive QA testing. These dependencies execute testing scripts, capture screenshots, and generate the structured report.

What's the best way to document web application bugs for a separate fixing team?

Using a report-only QA testing process to output structured reports is the best way to document web application bugs for a separate fixing team. These reports include repro steps and screenshots, ensuring the fixing team has everything needed without modifying the application.

Can I use this QA testing approach if my environment does not allow code fixes?

You can use this QA testing approach if your environment does not allow code fixes because it is specifically designed as a non-intrusive, report-only process. It systematically identifies and documents issues without making corrections to the application.