qa-only

Generate deterministic QA reports with health scores, screenshots, and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application in a non-intrusive way and produces a structured, evidence-rich QA report (health score, screenshots, and repro steps) without making any code changes.

Core Features & Use Cases

  • Non-intrusive QA passes that generate a publishable report with evidence for handoffs.
  • Comprehensive artifacts including health score, screenshots, and reproducible steps to reproduce issues.
  • Useful for requests like "just report bugs" or pre-release QA where no fixes are applied.

Quick Start

Run the QA workflow on the target app to generate a structured, evidence-backed report without applying any fixes.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a non-intrusive QA test on a live web application?

Run a non-intrusive QA test by executing a fixed pipeline against your live or local web deployment to capture health scores, screenshots, and reproducible steps without modifying source code.

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

A report-only QA pass is a non-intrusive testing workflow that systematically evaluates a web app and produces a structured, evidence-rich report without applying any code fixes. It is needed for pre-release checks or bug handoffs.

Can I generate a QA report with screenshots and reproducible steps without changing my code?

Yes, you can generate a QA report with screenshots and reproducible steps without changing code by running a non-intrusive testing workflow that captures evidence and health scores from your web application.

Does this QA workflow apply to local deployments or only live web apps?

This QA workflow applies to both local deployments and live web apps, allowing you to perform a thorough, non-intrusive pass that captures health scores and reproducible steps regardless of the deployment environment.

What's the best way to document bugs for handoff without fixing them myself?

The best way to document bugs for handoff without fixing them is to run a report-only QA workflow that generates a publishable report containing health scores, screenshots, and reproducible steps as evidence.