qa-only

Run report-only QA testing on web applications to generate structured issue reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the need to fix issues during QA runs by producing a structured report with health scores, screenshots, and repro steps.

Core Features & Use Cases

  • Verify application health without making changes.
  • Generate reproducible bug reports with steps and evidence.
  • Use during feature work, regression tests, and release readiness to surface issues.

Quick Start

Run a QA pass against the target web application to generate a structured issue 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 screenshots and repro steps for a web application?

To generate a bug report with screenshots and repro steps, perform a report-only QA testing pass against your web application to surface issues and capture structured evidence without applying fixes.

What is report-only QA testing and when do I need it?

Report-only QA testing is a process that verifies web application health by identifying issues and generating structured reports with health scores, screenshots, and reproducible steps without modifying code. You need it for feature work, regression checks, and release readiness.

Can I run manual QA testing for regression checks without making code changes?

Yes, you can run manual QA testing for regression checks without making code changes by using a report-only approach that applies browser automation to verify application health and output structured issue reports.

Does browser automation support capturing screenshots and health scores during a QA pass?

Browser automation supports capturing screenshots and health scores during a QA pass by executing evidence capture and reproducible report formatting, utilizing tools like Bash, Read, Write, AskUserQuestion, and WebSearch to document issues.

How do I calculate an application health score during release readiness testing?

You calculate an application health score during release readiness testing by executing a QA pass that evaluates feature behavior, captures evidence, and aggregates identified issues into a structured report format indicating overall stability.

What are the limitations of report-only QA testing?

The limitation of report-only QA testing is that it strictly identifies issues and generates reports without implementing fixes, meaning developers must separately address the surfaced bugs using the provided reproducible steps and screenshots.