qa-only

Test web applications and generate structured bug reports with health scores.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill qa-only-shaythegay13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/shaythegay13/serenity-pocket-app-final/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill qa-only-shaythegay13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro 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. Proactively suggest when the user wants a bug report without any code changes.

Core Features & Use Cases

  • Systematic QA testing of web applications without altering code
  • Structured reports including health score, screenshots, and reproducibility steps
  • Works with or without live environments; ideal for quick, non-fixing verification

Quick Start

Ask me to run a report-only QA analysis on your web app and generate a structured bug report with health score, screenshots, and reproducible 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 structured bug report for a web application without modifying any code?▼

Generate a structured bug report for a web application by running a report-only QA testing pass that enforces no code changes, focusing solely on documentation-style outputs like health scores, screenshots, and reproducibility steps.

What is report-only QA testing and when should I use it?▼

Report-only QA testing is a non-fixing verification pass on a new build that systematically tests a web application and produces a structured report with a health score, screenshots, and repro steps. Use it when you want to just report bugs without applying fixes.

Can I run a QA health check on my web app if I don't have a live environment?▼

Yes, you can run a QA health check without a live environment. This report-only testing process is designed to work with or without live environments, returning a comprehensive, review-ready bug report with evidence collection.

What's the best way to document bug reproducibility steps and capture screenshots during testing?▼

The best way to document bug reproducibility steps and capture screenshots is to use a systematic QA testing process that automatically collects evidence, calculates a health score, and compiles everything into a review-ready structured bug report.

What is the difference between report-only QA and a full test-fix-verify loop?▼

Report-only QA focuses exclusively on documentation and evidence collection, enforcing no code changes to produce a structured bug report. A full test-fix-verify loop actively fixes identified issues, requiring a different testing approach.

Does a report-only QA pass include a health score for the tested web application?▼

Yes, a report-only QA pass includes a health score for the tested web application. The resulting structured bug report combines this health score with screenshots and reproducibility steps to provide a comprehensive overview of build quality.