qa-only

Run a report-only QA pass and compile a structured findings document.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/zzxtbeta/design-handbook --skill qa-only-zzxtbeta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill qa-only-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistent, repeatable QA reporting that surfaces defects and health issues without modifying the codebase or delivering fixes.

Core Features & Use Cases

  • Report-only QA runs: Systematically tests a web application and compiles a structured report with health score, evidence, and repro steps.
  • Evidence-rich output: Includes screenshots, console checks, and traceable repro steps to guide triage.
  • Decision support for fixes: Helps product and engineering teams prioritize issues without performing any code changes during the QA pass.

Quick Start

Ask the agent to run a report-only QA pass on the current app and generate a structured bug report.

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 report-only QA pass on a web application?

A report-only QA pass systematically tests a web application across pages and features to compile a structured findings document. It generates evidence like screenshots and reproducible steps without applying any code fixes to the codebase.

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

Report-only QA testing identifies defects and health issues in a web application without modifying the codebase. You need it when you want consistent, repeatable defect reporting and decision support for prioritizing fixes without performing code changes during the testing pass.

Does automated QA testing generate evidence like screenshots and reproducible steps?

Yes, automated QA testing generates evidence-rich output that includes screenshots, console checks, and traceable reproducible steps. This structured bug report output guides developers and product teams during issue triage and fix prioritization.

Can I use this QA report for issue triage and automated test plans?

Yes, the QA report supports integration with automated test plans, browser checks, and issue triage. The compiled findings document provides decision support to help engineering and product teams prioritize issues for fixes.

What are the limitations of a report-only QA pass?

The primary limitation of a report-only QA pass is that it never fixes defects or modifies the codebase. It operates on demand to surface health issues and compile evidence, leaving actual code changes and fixes entirely to the developers.