qa-only

Generate a report-only web-app QA health report with score, screenshots, and reproduction steps.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill qa-only-uzumaki-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/uzumaki-inc/uzustack/tree/main/_upstream/gstack/qa-only
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill qa-only-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically performs QA checks on a web application and outputs a structured, report-only result that highlights issues without making any code changes.

Core Features & Use Cases

  • Generates a health-score based QA report including reproduction steps and screenshots for easy triage.
  • Provides a non-intrusive workflow when you need to surface bugs for reviews, audits, or handoffs without fixing code.
  • Supports proactive bug-reporting prompts when user request aligns with a bug discovery scenario.

Quick Start

Invoke the QA-only workflow by issuing the /qa command to generate a report-only QA pass on the current web application.

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

Report-only QA testing produces a structured web-app health report including a health score, screenshots, and reproduction steps without applying code fixes, ideal for surfacing bugs during reviews or audits.

Can I run a QA health check on my web app just to surface bugs for an audit?

Yes, you can run a report-only QA health check specifically designed to surface bugs for audits or handoffs, outputting a structured health report with reproduction steps and screenshots while leaving the codebase untouched.

How do I get reproduction steps and screenshots for web app issues automatically?

Automatic reproduction steps and screenshots are generated as part of the structured QA health report, which identifies web-app issues and outputs them with a health score for easy triage.

Does report-only QA testing modify my codebase during the bug discovery process?

No, report-only QA testing does not modify your codebase during bug discovery, as it is explicitly designed to output a deterministic health report and surface issues without applying any code changes.

What do I need to run a report-only QA workflow in the Claude Code environment?

To run the report-only QA workflow, you need the Claude Code environment, the gstack QA workflow, and allowed tools including Bash, Read, Write, AskUserQuestion, and WebSearch to produce the deterministic report.

When should I use a report-only QA workflow instead of automated bug fixing?

Use a report-only QA workflow instead of automated bug fixing when you need to surface issues for code reviews, audits, or team handoffs, requiring a non-intrusive health report with reproduction steps rather than code modifications.