qa-only

Run report-only QA testing on web applications and generate health score reports with screenshots and reproduction steps.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill qa-only-yahav123147
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/yahav123147/paid-ads-cro-skills/tree/main/skills/qa-only
Command: npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill qa-only-yahav123147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing whether a web app is healthy, broken, or regressions are happening, by running a structured QA pass and producing a clear report with evidence you can share.

Core Features & Use Cases

  • Report-only web app testing: Tests like a real user across pages and flows, then writes a structured health score report.
  • Evidence-first outputs: Includes screenshots and step-by-step repro steps so developers can reliably understand what happened.
  • No code changes: Never fixes, only diagnoses, making it safe to use when you explicitly want a bug report.

Quick Start

Ask for a report-only QA run by saying: "Run qa-only testing on https://myapp.com and produce a bug report with a health score, screenshots, and exact repro steps, but do not fix anything."

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 with repro steps for web testing without altering the codebase?

You can generate a bug report for web testing without code changes by running a report-only QA pass that exercises user journeys, then outputs a health score, screenshots, and exact reproduction steps. This ensures developers get evidence without any fixes applied.

What is report-only QA testing and when do I need it for my web application?

Report-only QA testing is the process of systematically exercising web app user journeys and state transitions to produce evidence of regressions. You need it when you want to diagnose issues and share structured reports without applying any remediation or code fixes.

How do I run regression checks on a web app and get a health score with screenshots?

Run regression checks by instructing the QA testing process to traverse your web app flows; it will systematically test state transitions and output a structured report containing a health score, screenshots, and step-by-step repro steps for any discovered bugs.

Can I use this QA testing approach to document user journeys without fixing the bugs?

Yes, this QA testing approach is explicitly designed to document user journeys without fixing bugs. It safely diagnoses issues by producing evidence and reproduction steps while strictly avoiding any code changes or remediation.

Does report-only web testing require any dependencies or specific components to run?

No, report-only web testing requires no dependencies or specific components to run. It operates independently to test your web application, generate a health score, and capture screenshots and repro steps.

What is the best way to share web app regression evidence with developers?

The best way to share regression evidence is to use a report-only QA workflow that captures screenshots and exact reproduction steps. This structured bug report gives developers reliable, evidence-first documentation of what happened without applying fixes.