qa-only

Generate structured QA reports with health scores, screenshots, and repro steps.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/studyzy/dev-agent-protocol --skill qa-only-studyzy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/studyzy/dev-agent-protocol/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/studyzy/dev-agent-protocol --skill qa-only-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.

Core Features & Use Cases

  • Structured QA reports with health scores, screenshots, and reproducible steps.
  • Supports diff-aware testing on feature branches or quick-mode exploration when URL is not provided.
  • Outputs project-scoped artifacts and baseline data to aid regression checks.

Quick Start

Provide the target URL and any auth details, then start the QA pass to generate a structured report without fixes.

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 without fixing code?▼

To generate a QA report without fixing code, run a report-only QA pass against your web application to systematically identify defects and output a structured report with health scores, screenshots, and a reproducible steps appendix.

What is a report-only QA testing pass for web applications?▼

A report-only QA testing pass systematically evaluates a web application to identify and describe reproducible defects and capture visual evidence, strictly producing a structured report without applying any code fixes.

How do I perform regression checks on a web application feature branch?▼

To perform regression checks on a feature branch, execute a diff-aware QA testing pass that compares current web application behavior against stored baseline data, outputting structured artifacts to aid regression comparison.

Does report-only QA testing support URL exploration when a target is not provided?▼

Yes, report-only QA testing supports quick-mode exploration when a target URL is not provided, allowing you to run a QA pass directly on a web application feature branch to identify and document defects.

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

Report-only QA testing strictly identifies and documents defects with repro steps and visual evidence without altering code, whereas a full test-fix-verify loop includes applying code fixes and retesting the web application.

Where are QA reports and baseline data stored during regression testing?▼

QA reports and baseline data for regression testing are stored as project-scoped artifacts under the project's .gstack/qa-reports directory, enabling structured evidence-backed reporting and future regression comparison.