qa-only

Simulate user interactions to produce a structured defect report with screenshots and reproduction steps.

Updated Mar 13, 2026

Search Tags:#testing #qa #evidence #web-app #bug-report #repro-steps

Ready to run

npx skills add https://github.com/soyasis/gstack-private --skill qa-only-soyasis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/soyasis/gstack-private/tree/main/qa-only
Command: npx skills add https://github.com/soyasis/gstack-private --skill qa-only-soyasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need to verify web applications from a user's perspective and produce a structured report with evidence, without modifying the codebase. This skill ensures testers can consistently document issues and reproduce steps.

Core Features & Use Cases

Manual exploratory testing guided by a repeatable workflow.
Automated evidence collection: screenshots, console logs, and reproduction steps.
Structured reporting including a health score and issue taxonomy for remediation prioritization.
Use Case: A team asks for a "report-only" QA pass on a new checkout flow to surface defects without changing any code.

Quick Start

Run a report-only QA session against the target web application and generate a structured, evidence-backed defect report without applying any fixes.

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 simulates real user interactions to identify defects and generates a structured report with reproduction steps, evidentiary screenshots, and a health score without modifying code.

What is structured defect reporting in manual QA testing?▼

Structured defect reporting in manual QA testing documents issues found during web application exploration by capturing evidence, console logs, and reproduction steps to produce a health score for remediation prioritization.

Can I capture screenshots and console logs during exploratory web app testing?▼

Yes, you can capture screenshots and console logs during exploratory web app testing by logging steps and using provided tools to collect automated evidence for a final structured defect report.

Does this QA testing approach make any code changes to the application?▼

No, this QA testing approach does not make any code changes; it focuses exclusively on surfacing web application issues, capturing evidence, and composing a final defect report for remediation.

What is the best way to document reproduction steps for a web app bug report?▼

The best way to document reproduction steps for a web app bug report is to log real user interactions during manual QA testing, capturing structured evidence and console logs to ensure issues are reproducible.