qa-only

Test web applications by clicking controls, filling forms, and verifying state changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web teams often rely on manual QA that is slow, inconsistent, and hard to reproduce. This Skill conducts non-intrusive, real-user-like testing and outputs a structured report with evidence, health score, and reproduction steps, without applying any fixes.

Core Features & Use Cases

  • Non-intrusive QA that does not modify code or deploy changes.
  • Generates a consolidated report with health score, screenshots, and step-by-step repros.
  • Use cases include quick sanity checks on new builds or regression verification on feature branches.

Quick Start

Run the qa-only skill to start a report-only QA pass and save results to .gstack/qa-reports.

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 with reproducible steps for manual web app testing?

Manual web app testing generates a structured bug report with step-by-step reproducible steps, screenshots, and a health score by clicking controls and verifying state changes. It operates on a target URL without modifying source code.

Can I run QA testing on a feature branch without modifying my source code?

QA testing on a feature branch runs non-intrusively without modifying source code or deploying changes. It supports diff-aware mode to verify regressions and outputs evidence for handoff.

What is structured QA report generation and when do I need screenshots as evidence?

Structured QA report generation provides a health score, screenshots, and reproduction steps after testing web applications like a real user. You need this evidence for handoff when performing quick sanity checks or regression verification.

How do I perform a quick sanity check on a new build using automated repro steps?

A quick sanity check on a new build uses automated testing to click controls and fill forms, generating reproducible steps and a health score. The report-only pass saves results for team handoff.

Does web app QA testing work with authentication and diff-aware mode for regression testing?

Web app QA testing supports optional authentication and diff-aware mode for regression testing on feature branches. It tests applications like a real user and saves consolidated reports to a specified directory.

What are the limitations of report-only QA testing for web applications?

Report-only QA testing never modifies source code or applies fixes; it strictly surfaces defects. It outputs structured evidence and a final report, requiring developers to handle the actual remediation.