qa-only

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

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill qa-only-jesse-l-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill qa-only-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you need thorough QA validation without making any code changes or fixes, this skill runs scripted tests and returns a structured report with a health score, evidence, and reproducible steps.

Core Features & Use Cases

  • Systematic web app testing that produces a health score, evidence, and reproducible repro steps without applying fixes.
  • Works for bug-report-heavy workflows, acceptance testing, and regression checks on demand.
  • Use when you want a detached QA readout, or to surface issues before handing off to a fix process.

Quick Start

Ask Claude to run the qa-only skill on the target app to generate a report without applying any changes.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run automated QA tests on a web app without making code changes?

Report-only QA testing executes scripted web application tests to produce a structured health report with a health score, screenshots, and reproduction steps without applying fixes.

What is a QA health score and how does it help with bug discovery?

A QA health score is a structured metric generated by testing web app pages and flows, summarizing application stability alongside evidence and reproduction steps for discovered bugs.

Can I use this QA skill for regression checks and acceptance testing?

Yes, report-only QA testing works for regression checks, acceptance testing, and bug-report-heavy workflows by generating reproducible test artifacts across web app pages and flows.

How do I generate a structured test report with reproduction steps for my web application?

Run detached QA validation on your target web app to surface issues and output a structured test report containing a health score, screenshots, and detailed reproduction steps.

Does report-only QA testing require any dependencies or external components to run?

No external dependencies are required; the QA testing process relies on built-in Bash, Read, Write, and WebSearch tools to execute tests and generate the health report.

When should I use a report-only QA test instead of an automated fix process?

Use report-only QA testing when you need a detached readout to surface issues before handing off to a fix process, or when you need reproducible test artifacts without modifying code.