qa-only

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application and produces a structured report with a health score, screenshots, and reproduction steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.

Core Features & Use Cases

  • Generates a comprehensive QA report including health score, evidence screenshots, and reproducible steps.
  • Tests web applications without modifying source code, suitable for "just report bugs" or "qa report only" scenarios.
  • Fits into existing QA pipelines and supports ad-hoc/manual QA passes when a full fix-verify cycle is not desired.

Quick Start

Run the qa-only skill against your target web app to produce a structured report with health score, screenshots, and repro steps.

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 report for a web app without modifying the source code?

A report-only QA testing process generates a structured report with a health score, evidence screenshots, and reproduction steps without applying fixes. Use this when asked to "just report bugs" or perform a manual QA pass.

What is the best way to report bugs with reproduction steps and screenshots?

The best way to report bugs with reproduction steps is to automate report-only QA testing, which systematically captures evidence screenshots and documents reproducible steps in a structured format without attempting to fix the issues.

When should I use a report-only QA pass instead of a full test-fix-verify loop?

You should use a report-only QA pass instead of a full test-fix-verify loop when you need to systematically test a web application and produce a structured report with a health score and screenshots, but explicitly do not want to apply any fixes or modifications.

Does report-only QA testing produce a health score for web applications?

Yes, report-only QA testing produces a comprehensive QA report that includes a health score, evidence screenshots, and reproduction steps for web applications, providing a clear metric of application quality without altering the source code.

Can I use this reporting approach for ad-hoc manual QA passes in existing pipelines?

Yes, you can use report-only QA testing for ad-hoc manual QA passes within existing pipelines. It fits seamlessly by generating structured reports with health scores and reproducible steps when a full fix-verify cycle is not desired.