qa-only

Generate a report-only QA test with health score, screenshots, and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides deterministic, report-only QA testing for web applications, producing a structured health report with evidence while never applying fixes or code changes.

Core Features & Use Cases

  • Automated, on-demand QA passes that generate a health score, screenshots, and a reproducible set of steps to reproduce issues.
  • Works in environments where you want visibility into defects without modifying source code, enabling quick bug triage and hand-off to developers.
  • Integrates with the /qa workflow for the full test-fix-verify loop when needed.

Quick Start

Invoke the qa-only skill against your target URL to generate a complete QA 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 QA report with screenshots and repro steps for a web app without changing the code?

You can generate a report-only QA test for a web app to produce a health score, screenshots, and repro steps without applying fixes. This on-demand testing workflow gives you visibility into defects for quick triage while leaving the source code untouched.

What is report-only QA testing and when do I need it for bug triage?

Report-only QA testing is a deterministic process that identifies defects and produces a structured health report with evidence without modifying source code. You need it when you want visibility into bugs for quick triage and developer hand-off rather than automated code fixes.

How do I run an on-demand QA test on a specific web application URL?

You invoke the qa-only workflow against your target web application URL to run deterministic test steps and collect artifacts. This generates a complete, formal QA report with a health score and screenshots on demand.

Does report-only QA testing automatically fix the bugs it finds in my web app?

No, report-only QA testing never applies fixes or code changes to your web app. It strictly coordinates test steps, artifact collection, and formal reporting to provide a health score and reproducible steps for developer hand-off.

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

Report-only QA testing generates a structured health report with screenshots and repro steps without modifying code. A full test-fix-verify loop, available via a standard QA workflow, actually applies fixes and verifies them after testing.

Can I use automated QA testing in environments where I cannot modify the source code?

Yes, automated report-only QA testing works in environments where you cannot modify source code. It enables on-demand defect visibility by generating a health score, screenshots, and repro steps for bug triage without applying any code changes.