qa-only

Run report-only QA checks on web applications and generate structured bug reports.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill qa-only-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/gstack/qa-only
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill qa-only-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you systematically test a web application and produce a clear, structured QA report when you want visibility into issues without making any fixes.

Core Features & Use Cases

  • Report-only QA testing: Runs test scenarios and documents findings as a structured report, including a health score, screenshots, and reproducible steps, while never applying changes.
  • Bug repro guidance: Produces actionable repro steps so developers can quickly confirm and investigate the bug.
  • No-fix workflow: Best for requests like “just report bugs” or “qa report only”, and for situations where you explicitly do not want code changes or hotfixes.
  • Proactive suggestion of QA reporting: When the user wants a bug report without code changes, it nudges toward the report-only workflow rather than a fix loop.

Quick Start

Use qa-only to run report-only testing on the web app you describe, then return a health score, screenshots, and step-by-step repro instructions without making 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 bug report with repro steps for web testing?

To generate a bug report with repro steps for web testing, you need a report-only workflow that runs systematic checks and captures evidence. This produces a structured document containing a health score, screenshots, and step-by-step reproduction instructions without applying code fixes.

What is a health score in QA reporting?

A health score in QA reporting is a metric generated by systematically testing a web application to quantify its overall stability. It provides immediate visibility into application issues alongside structured evidence like screenshots and actionable reproduction steps.

Can I run QA testing without making any code changes?

Yes, you can run QA testing without making code changes by using a no-fix workflow. This approach constrains execution to observation and reporting only, allowing you to confirm behavior and capture bug evidence while leaving the source code completely untouched.

What is the best way to prepare bug reproduction steps for developer triage?

The best way to prepare bug reproduction steps for developer triage is to use a report-only QA workflow that systematically captures the exact actions leading to the issue. This generates actionable, step-by-step instructions and screenshots for quick developer confirmation.

How do I capture screenshots during web application bug reproduction?

To capture screenshots during web application bug reproduction, execute a systematic testing check that automatically records visual evidence. These screenshots are then embedded directly into your structured QA report to visually validate the documented reproduction steps.