qa-only

Generate structured QA reports with health scores, screenshots, and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates manual QA testing by triggering comprehensive bug reports without applying any code changes.

Core Features & Use Cases

  • Generates a structured QA report with a health score, evidence (screenshots), and reproducible steps.
  • Reports-only mode: use when asked to "just report bugs" or "qa report only"; does not fix anything.
  • Proactively suggests issues when requested, but never makes changes to the live system.

Quick Start

To run it, type /qa-only when you want a complete bug-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 generate a structured bug report for a web application without applying fixes?

To generate a bug report without applying code fixes, trigger the /qa-only command in a browser-based testing environment. The process outputs structured reproducible steps, screenshots, and a health score to the .gstack/qa-reports directory.

What is a QA health score and how does it evaluate web app stability?

A QA health score is an automated metric generated during manual testing to evaluate web app stability. It accompanies evidence like screenshots and reproducible steps, providing a quantifiable summary of the application's current bug severity.

Do I need a specific browser environment to run manual QA tests and export bug reports?

Yes, you need a browser-based testing environment to run manual QA tests and export bug reports. The automated testing workflow requires this environment to capture screenshots and save the structured reports to the .gstack/qa-reports directory.

Can I use this approach to proactively identify web app issues without modifying the codebase?

Yes, you can proactively identify web app issues without modifying the codebase. The reports-only mode suggests issues and generates a health score but never makes changes to the live system, ensuring a read-only testing process.

What are the limitations of using an automated manual QA testing workflow?

The primary limitation of this automated manual QA testing workflow is that it cannot apply code fixes or make changes to the live system. It strictly generates bug reports, reproducible steps, and screenshots for separate remediation.