qa-only

Automate report-only testing of web applications to generate health reports with screenshots and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA-only automates report-only testing to systematically test a web application and produce a structured report with health score, screenshots, and repro steps — but never fixes anything.

Core Features & Use Cases

  • Structured health reports
  • Automated screenshot capture
  • Repro-step documentation for issues found without code changes

Quick Start

Run qa-only on a project to generate a health score, screenshots, and a repro steps report 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 automate QA testing to generate bug reports without fixing the source code?

Automated report-only QA testing systematically detects web application issues and produces structured health reports, screenshots, and repro steps without altering the source code.

Can I capture screenshots and repro steps automatically during web application testing?

Yes, automated browser-based QA testing captures screenshots and documents repro steps for detected issues, generating a structured health report for your web application.

Does report-only testing require a specific browser-based testing harness?

Yes, report-only QA testing requires a browser-based testing harness and tools to systematically capture screenshots, health scores, and repro steps across pages and interactive flows.

What is a structured health score in web application QA testing?

A structured health score is an automated metric generated by report-only QA testing that summarizes the overall condition of a web application after systematically testing navigations and interactive flows.

When should I use report-only QA testing instead of automated fixing?

Use report-only QA testing when you need documented bug reports with repro steps and screenshots for web applications, but want to ensure no changes or fixes are applied to the source code.