qa-only

Test web applications and generate a structured QA report without applying fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application in a report-only mode, generating a structured QA report that includes a health score, screenshots, and reproducible steps, but never applies fixes.

Core Features & Use Cases

  • Structured, non-invasive QA: tests produce a health score, screenshots, and reproducible steps without making code changes.
  • Trigger-driven workflow: responds to "qa report only", "just report bugs", or "test but don't fix" for quick audits.
  • Safe integration with full test loops: when used with /qa for the full test-fix-verify cycle, it supports planning and evidence gathering without modifications to source.

Quick Start

Invoke the qa-only skill with the trigger qa report only to generate a structured QA report without applying 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 for a web app without applying code fixes?

To generate a bug report without applying fixes, you run a report-only QA test. This process audits your web application to produce a structured report containing a health score, screenshots, and reproducible steps while ensuring the source code remains completely unmodified.

What is included in a structured non-invasive web application QA report?

A structured non-invasive QA report includes a quantified health score, captured screenshots, and detailed reproducible steps. It systematically documents the testing evidence and identified issues without making any changes to the application's underlying source code.

How do I run a report-only QA audit on a web application?

You run a report-only QA audit by triggering a non-invasive testing workflow with commands like "qa report only" or "just report bugs". The system scripts tests, collects evidence, and prompts you for decisions to build the final health score report.

Can I use report-only QA testing as part of a full test and fix cycle?

Yes, you can use report-only QA testing within a full test-fix-verify cycle. When following a complete workflow, it supports planning and evidence gathering phases by generating bug reports and screenshots without modifying source code.

What toolset is required to run automated QA tests and collect evidence?

Running automated QA tests and collecting evidence requires a compatible toolset including Bash, Read, Write, AskUserQuestion, and WebSearch. These tools script the tests, capture screenshots, generate reports, and prompt the user when decisions are needed.