qa-only

Generate structured health reports with screenshots and repro steps for web applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA-only testing isolates verification from remediation, producing a structured report with health metrics, screenshots, and reproduction steps without applying any fixes.

Core Features & Use Cases

  • Conduct read-only QA passes on web applications and generate a concise health report.
  • Include screenshots, reproducible steps, and a health score to guide stakeholders.
  • Proactively suggest when a user asks for a bug report without code changes (qa report only).

Quick Start

Invoke the QA-only workflow on a target web app and generate a structured bug-reporting document.

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 bug report for a web app without applying fixes?

A read-only QA pass isolates verification from remediation to produce a structured bug report. It generates health metrics, screenshots, and reproduction steps for your web app without applying any code fixes.

What is report-only QA testing and when should I use it?

Report-only QA testing is the process of evaluating a web application to identify issues and generate a health report without making code changes. You should use it when you need to document bugs and reproducible steps for stakeholders before remediation begins.

How do I document bug reproduction steps and capture screenshots during a web application QA evaluation?

You can document bug reproduction steps and capture screenshots by running an automated read-only QA evaluation on your web application. This workflow generates a structured report containing health scores, screenshots, and detailed repro steps for identified issues.

Does the qa report only workflow support planning a full test-fix-verify loop?

Yes, the qa report only workflow supports planning the full test-fix-verify loop through its dedicated endpoint. It generates the initial structured health report and bug documentation needed to guide the subsequent fix and verify phases.

Can I use this QA testing workflow to just report bugs without modifying my web application code?

Yes, you can use this workflow to just report bugs without modifying your web application code. It enforces a strict read-only testing approach that captures screenshots and repro steps while applying safety gating to prevent any fixes.