qa-only

Automate report-only QA testing for web applications with screenshots and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing automates systematic checks of a web application and produces a structured report with a 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.

Core Features & Use Cases

  • Non-intrusive QA checks that run against a live app without making changes.
  • Generates a structured health report with screenshots and reproducible steps.
  • Voice triggers and commands for quick bug reporting workflows.

Quick Start

Provide a single instruction: "Request a report-only QA pass on the target web app and generate a structured results document."

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 applying any fixes?

Report-only QA testing automates systematic checks of a live web application to produce a structured health report with screenshots and repro steps, ensuring no fixes are applied to the codebase.

Can I run a non-intrusive regression sweep on a live web application?

Yes, report-only QA testing runs non-intrusive checks against a live web application to capture evidence and document clear repro steps, making it suitable for quick regression sweeps without altering the environment.

What is the best way to document bug repro steps with screenshots automatically?

Automated report-only QA testing validates test coverage and captures both screenshots and clear reproducible steps into a structured health report for bug investigations.

Does report-only QA testing modify the target web application during a sanity check?

No, report-only QA testing uses non-invasive tooling to perform sanity checks, ensuring the target web application remains completely unmodified while generating the health report.

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

Use report-only QA testing when you need to validate test coverage and document repro steps for bugs without implementing fixes, such as during initial bug investigations or strict regression sweeps.