qa-only

Test web apps and generate structured QA reports with screenshots and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or to test but don't fix. For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

Core Features & Use Cases

  • Systematic, non-fix QA passes that simulate user interactions and verify states without altering code.
  • Structured reports including health scores, evidence (screenshots, repro steps), and clear failure reasons for handoff.
  • Proactively suggest bug reports when requested, guiding users to next steps.

Quick Start

Run the QA workflow against the target URL to generate a structured report with evidence, without applying any code changes.

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 for a web app without applying code fixes?

To generate a bug report without code fixes, run a report-only QA workflow against your web app. It systematically tests the application, simulates user interactions, and produces a structured report with health scores, screenshots, and repro steps while ensuring no code changes are made.

What is report-only QA testing and when should I use it?

Report-only QA testing is the process of identifying and documenting web app issues without applying fixes. Use it when you need to systematically collect evidence, health scores, and repro steps for handoff or future regression tests, ensuring the codebase remains completely unaltered.

Does the QA report include screenshots and reproduction steps for identified bugs?

Yes, the QA report includes screenshots and reproduction steps. It systematically collects evidence by interacting with the web app to reproduce issues, generating a structured handoff report complete with health scores, clear failure reasons, and detailed repro steps for future regression testing.

Can I test a specific scope of my web application or does it only scan the full site?

You can test both a full site and focused scopes of your web application. The QA workflow applies the testing logic to your specified target scope, systematically reproducing issues and collecting structured evidence without applying any code fixes to the application.

How do I document QA findings for developer handoff and future regression tests?

To document QA findings for handoff, the workflow returns a reproducible report containing structured failure reasons, health scores, screenshots, and repro steps. This structured output is designed for seamless developer handoff and suitable for integration into future regression tests.

What's the difference between report-only QA testing and a full test-fix-verify loop?

Report-only QA testing strictly documents issues by collecting evidence, screenshots, and repro steps without altering code. A full test-fix-verify loop identifies bugs and applies code changes to resolve them, whereas this report-only approach ensures no code changes are made during the process.