qa-only

Identify web application defects and generate a QA report with health score, screenshots, and reproducible steps.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill qa-only-computerconnection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-qa-only
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill qa-only-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the risk of introducing fixes while validating the behavior of a web application, delivering structured reports that include health scores, evidence, and reproducible steps.

Core Features & Use Cases

  • Non-intrusive QA runs that collect a health score, screenshots, and reproducible steps without making code changes.
  • Generates a consistent, shareable QA report suitable for handoffs to developers, product, or QA teams.
  • Use cases include quick smoke checks on new builds, regression vetting, and evidence-backed bug reporting for desktop and mobile experiences.

Quick Start

Run the qa-only skill against your target URL to generate a structured, report-only QA report with evidence and screenshots.

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 QA report with screenshots and repro steps without fixing code?

Report-only QA testing identifies defects in a web application and generates a comprehensive QA report with a health score, screenshots, and reproducible steps without applying any fixes. It runs non-intrusively to collect evidence for bug reporting.

What is a non-intrusive QA health score and when do I need it for web testing?

A non-intrusive QA health score evaluates web application behavior without making code changes. You need it for quick smoke checks on new builds, regression vetting, and evidence-backed bug reporting across desktop and mobile experiences.

Can I use report-only QA for both desktop and mobile web application sanity checks?

Yes, report-only QA applies to quick sanity checks, regression vetting, and evidence-based bug reporting for both desktop and mobile web experiences. It captures screenshots and reproducible steps across these platforms without applying fixes.

How do I capture evidence and reproducible steps for a bug report without modifying the application?

Run a non-intrusive QA session against your target URL to capture screenshots and generate reproducible steps. The process redacts sensitive data and outputs a consistent, shareable report suitable for developer handoffs without modifying code.

Does report-only QA testing redact sensitive data when capturing screenshots?

Yes, report-only QA testing includes redaction of sensitive data during evidence capture and screenshot collection. This ensures the generated QA report with health scores and reproducible steps remains safe for sharing across development and product teams.

What's the best way to run a quick smoke check on a new build without risking code changes?

Report-only QA is the best way to run quick smoke checks on new builds because it validates behavior and generates structured reports with health scores without applying any fixes. It eliminates the risk of introducing changes during testing.