qa-only

Evaluate web applications and generate structured QA reports with health scores and evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing focuses on systematically evaluating a web application and producing a structured quality report with a health score, reproducible steps, and evidence such as screenshots — but it never performs fixes.

Core Features & Use Cases

  • Non-destructive testing: evaluates the app and reports issues without applying changes.
  • Structured reports: health score, repro steps, screenshots, and guidance for debugging.
  • Use Case: run a quick QA sweep after a new release to surface regressions before shipping.

Quick Start

Request a report-only QA pass on your web app and generate a structured bug report with evidence.

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 QA test on a web app without applying any code fixes?

Report-only QA testing evaluates a web application and generates a structured bug report with health scores, reproducible steps, and screenshot evidence without applying any remediation fixes.

What is included in a structured QA report for web applications?

A structured QA report includes a web app health score, evidence screenshots, and detailed reproducible steps to guide debugging, specifically avoiding any remediation attempts.

Can I run a non-destructive QA sweep after a new web app release?

You can run a non-destructive QA sweep after a new release to systematically evaluate the web app and surface regressions before shipping without modifying the codebase.

What's the best way to generate bug reports with reproduction steps and screenshots?

Generating bug reports with reproducible steps and screenshot evidence is best handled by report-only QA testing, which systematically evaluates web app issues without attempting fixes.

When should I use a report-only QA approach instead of a full fix loop?

Use a report-only QA approach when you request only a structured quality report and desire to avoid a full fix loop, preventing any code remediation during the bug identification phase.

How do I surface web app regressions before shipping a release?

Running a quick QA sweep evaluates the web app to surface regressions before shipping, returning a structured report with health scores and evidence rather than applying fixes.