qa-only

Automates report-only QA testing for web applications, producing a structured bug report.

4|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/florianhorner/mammamiradio --skill qa-only-florianhorner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/florianhorner/mammamiradio/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/florianhorner/mammamiradio --skill qa-only-florianhorner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need non-invasive checks that surface issues without altering product code, delivering a consistent report you can act on.

Core Features & Use Cases

  • Structured QA reports with a health score, screenshots, and reproducible steps.
  • Triggered when asked for a bug report, qa report only, or test but don't fix, and never modifies production.
  • Deterministic test execution using Bash, Read, Write, AskUserQuestion and WebSearch to surface issues quickly.

Quick Start

Start a report-only QA run against your web app to generate a structured health report.

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 structured QA bug report with screenshots and repro steps?

You can generate a structured QA bug report by running a report-only testing pass against your web application to capture screenshots, reproducible steps, and a health score without applying fixes.

Can I run automated QA testing without modifying my production code?

Yes, you can run non-invasive automated QA testing that surfaces issues and captures health metrics without altering your product code or applying any fixes.

What is a report-only QA pass and when do I need one?

A report-only QA pass is a non-invasive testing process that surfaces issues across features and captures health metrics, needed when you want to deliver a consistent report for stakeholders to act on.

How do I capture a health score for my web application features?

You capture a health score by executing deterministic test passes using Bash, Read, Write, and WebSearch to quickly surface issues and output a clean, consumable health report.

Does report-only QA testing work for surfacing issues across multiple web features?

Yes, report-only QA testing works for surfacing issues across web application features by running deterministic checks and exporting reproducible steps and visuals for stakeholders.

What are the limitations of running a test but don't fix approach for QA?

The limitation of this test but don't fix approach is that it strictly produces a report with a health score and repro steps while never modifying production code or applying fixes.