qa-only

Automate browser-based QA testing and generate structured reports with screenshots and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing often reveals issues, but teams need a clear, reproducible report without applying any fixes. This skill enables automated, structured QA reports including health scores, screenshots, and repro steps, while never modifying the application.

Core Features & Use Cases

  • Automated, browser-based QA that systematically exercises the app and accumulates evidence.
  • Evidence-rich reports with screenshots, console logs, and step-by-step repro guidance for stakeholders.
  • Use Case: When asked to "just report bugs" or "qa report only," generate a complete QA narrative without code changes.

Quick Start

Run /qa against your app to generate a complete QA report.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate automated QA reports with screenshots and console logs?

Automated browser-based QA reports with screenshots and console logs are generated by systematically exercising your web application to capture step-by-step repro guidance and evidence without applying any code fixes.

What is diff-aware QA testing and when should I use it?

Diff-aware QA testing executes automated browser tests exclusively on feature branches without a provided URL, capturing targeted regression evidence and baseline.json outputs to isolate newly introduced issues.

Does QA reporting modify my application code during testing?

QA reporting does not modify application code during testing, ensuring structured reports including health scores, screenshots, and console logs are produced safely without altering the deployment.

How do I run full-mode browser QA testing against a deployed URL?

Full-mode browser QA testing runs against a deployed URL by executing the /qa command, systematically capturing application screenshots, console logs, and repro steps to output a complete QA narrative.

What do I need to set up automated browser-based QA report generation?

Automated browser-based QA report generation requires a browse binary and optional QA scripts with references directories, outputting structured health scores and regression baselines to .gemstack/qa-reports.

Can I use automated QA reporting to generate bug reports without fixing them?

Automated QA reporting generates structured bug reports without fixing them, systematically exercising the app to accumulate evidence-rich narratives including health scores and repro steps for stakeholders.