qa-only

Test a web application and generate a structured QA report with health score, screenshots, and repro steps.

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

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 "test but don't fix". For the full test-fix-verify loop, use /qa instead.

Core Features & Use Cases

  • Performs a thorough, report-only QA pass on a web application.
  • Generates a structured report including a health score, evidence (screenshots), and reproducible steps.
  • Proactively suggests improvements without modifying code, and supports scenarios like "qa report only" or "test but don't fix".

Quick Start

Invoke the QA-only skill on your app to generate a report-only QA run that yields the health score, screenshots, and reproducible steps.

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 QA report for a web application without modifying any code?

A report-only QA pass systematically tests your web application to produce a structured report with a health score, screenshots, and reproducible steps while never modifying the application code.

What is the difference between a report-only QA pass and a full test-fix-verify loop?

Report-only QA strictly finds issues and produces evidence like screenshots and repro steps without altering code, whereas a full test-fix-verify loop includes implementing code fixes and verifying that those changes resolve the discovered defects.

How do I get reproducible steps and screenshots for bugs found during web testing?

You can get reproducible steps and screenshots by running a structured QA testing pass that systematically evaluates the web application, logs the exact actions needed to trigger defects, and captures visual evidence of the issues.

Can I test my web application and just report bugs without fixing them?

Yes, you can use a report-only QA skill designed to test but not fix, proactively suggesting improvements and outputting a formal bug report for stakeholders without making any code changes.

How do I export a formal QA report with a health score for stakeholders?

You can export a formal QA report by running a QA pass that generates a health score and structured findings, integrating with a stack tool to format and export the final documentation for stakeholder review.

When should I use a report-only testing approach instead of an automated fixing process?

You should use a report-only testing approach when explicitly asked to 'just report bugs' or 'qa report only', ensuring you capture defects and suggest improvements without the risk or commitment of altering the codebase.