qa-only

Run report-only QA testing on web applications and generate health scores, screenshots, and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This QA skill performs report-only testing to identify issues in a web application and produce a structured bug report, health score, and visual evidence without applying any fixes.

Core Features & Use Cases

  • Systematic, report-only QA passes that do not modify the codebase.
  • Generates a health score, screenshots, and a reproducible set of steps to reproduce issues.
  • Use Case: during release readiness, bug triage, or when you need a fast, non-intrusive QA snapshot.

Quick Start

Invoke qa-only to run a structured, report-only QA pass that outputs a health score, reproducible steps, and visuals without applying 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 report-only QA testing on a web application without modifying the codebase?

Report-only QA testing systematically identifies bugs in a web application and generates a health score, screenshots, and reproducible steps without applying any code fixes to the codebase.

What is included in a bug report for web app release readiness?

A bug report for web app release readiness includes a calculated health score, visual screenshots, and structured, reproducible steps to replicate each identified issue.

Can I use this QA testing approach for bug triage without fixing the issues?

Yes, this report-only QA approach is designed specifically for bug triage scenarios, allowing you to identify and document issues with a health score and visuals without applying fixes.

When do I need a non-intrusive QA snapshot for my web application?

You need a non-intrusive QA snapshot during release readiness, bug triage, or QA cycles when you require a fast assessment of web application health without altering the code.

Does this bug report testing generate reproducible steps for identified issues?

Yes, the bug report testing generates a structured set of reproducible repro steps, alongside a health score and screenshots, for every issue found during the QA run.

What are the limitations of report-only web app testing?

Report-only web app testing is limited to identifying and documenting bugs; it does not apply fixes or modify the codebase, serving strictly as a non-intrusive assessment tool.