qa-only

Test a web application and generate a structured QA report with health score, screenshots, and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams and developers often need reproducible bug reports without altering code. This skill executes systematic web app testing and returns a structured report including a health score, evidence screenshots, and clear repro steps, without applying fixes.

Core Features & Use Cases

  • Systematic web app testing that produces a health score, screenshots, and repro steps.
  • Useful when asked to "just report bugs", "qa report only", or "test but don't fix"; can complement /qa workflows.
  • Proactively suggests a report-only path when a user requests a bug report without code changes.

Quick Start

Run the qa-only skill on the active web application to generate a structured 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 generate a bug report for a web app without applying code fixes?

To generate a bug report without code fixes, you can run a report-only QA test that systematically analyzes the web app, calculates a health score, captures screenshots, and documents repro steps while keeping modifications out of scope.

What is a health score in web application testing?

A health score in web application testing is a structured metric generated by systematically evaluating a web app to quantify its overall stability, providing a quick reference point in the QA report alongside evidence and reproduction steps.

How do I get structured repro steps for regression verification?

Structured repro steps for regression verification are produced by executing systematic browser automation tasks on your web app, capturing the exact interactions needed to trigger the bug, and formatting them into a shareable QA report.

Can I use automation to test a new build and just report bugs?

Yes, you can use automation to test a new build and just report bugs by running a QA-only workflow that captures evidence and formats findings into a structured report, specifically designed to ensure no code changes are applied during the process.

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

You should use a report-only QA test instead of automated bug fixing when you need reproducible evidence and a health score for regression verification or a new PR, ensuring the testing environment remains unaltered by code modifications.