qa-only

Test a web application and generate a structured bug report with health score, screenshots, and reproduction steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application and produces a structured bug report with health score, screenshots, and reproduction steps — but never fixes anything. Use when you want a report-only QA pass, such as "qa report only" or "test but don't fix", or when you need evidence without altering code.

Core Features & Use Cases

  • Non-intrusive, reproduceable QA checks that gather evidence (screenshots, health score, repro steps) without applying fixes.
  • Generates a structured bug report suitable for handoff to developers and stakeholders.
  • Use Case: run a quick report-only assessment on a live app, or generate a regression evidence bundle from a PR.
  • If you need a full fix-verify loop, use /qa to switch modes.

Quick Start

Run a report-only QA pass on the current app state to generate a structured bug report with health score, screenshots, and repro steps.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a report-only QA test on a web app without applying fixes?

A report-only QA test systematically checks a web app and generates a structured bug report with health scores, screenshots, and reproduction steps without modifying production code. It uses built-in tooling to orchestrate tests and collect evidence automatically.

What is a structured bug report with reproduction steps used for?

A structured bug report with reproduction steps is used for developer handoff and stakeholder review. It provides a reproducible evidence bundle containing health scores and screenshots, ensuring bugs found during web app testing can be independently verified and fixed.

Can I generate a regression evidence bundle from a PR diff?

Yes, you can generate a regression evidence bundle from a PR diff. The QA testing process operates on a diff-based context to collect evidence and produce a structured report, targeting situations where you need to verify changes without altering code.

Does this QA testing approach work on a live web application?

Yes, this QA testing approach works on a live web application. It performs non-intrusive, reproducible checks to gather evidence like screenshots and health scores, operating safely on live apps without applying any code fixes.

When should I not use a report-only QA pass?

You should not use a report-only QA pass when you need a full fix-verify loop. This approach strictly produces a report and never modifies production code, so if you need automated fixes applied directly to your web app, you should switch modes.