qa-only

Generate report-only QA testing workflows for web applications with health scores and screenshots.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill qa-only-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill qa-only-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a report-only QA testing workflow that documents issues without making any code changes, enabling fast, non-destructive validation.

Core Features & Use Cases

  • Non-destructive testing that generates structured bug reports with evidence.
  • Health-score style assessment, screenshots, and precise repro steps.
  • Ideal for requests like "just report bugs" or "qa report only" when a full fix loop is not desired.

Quick Start

Run the qa command to generate a complete, no-fix QA report.

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 bug report without modifying my web application code?

A QA-only testing workflow assesses your web application by running deterministic test orchestration to produce a health score, capture screenshots, and document reproducible steps. This process strictly enforces a no-fix policy to ensure non-destructive validation.

Can I run QA testing on both local and remote deployments?

Yes, the QA testing workflow supports running tests on demand across both local and remote web application deployments. It orchestrates deterministic tests against your specified environment to gather evidence and generate reports.

What evidence is included in a non-destructive QA report?

A non-destructive QA report includes a health score assessment, captured screenshots, and precise reproducible steps. This structured evidence is gathered during deterministic test orchestration to document bugs accurately.

When should I use a report-only QA workflow instead of a full fix loop?

You should use a report-only QA workflow when you need fast, non-destructive validation and want to document issues without making code changes. It is ideal for requests like generating a QA report when a full fix loop is not desired.