qa-only

Execute report-only QA testing for web applications with health scores and screenshots.

Updated Apr 3, 2026

Search Tags:#automation #testing #qa #reporting #quality-assurance #web-app #bug-report

Ready to run

npx skills add https://github.com/lyh2/gstack-deepseek --skill qa-only-lyh2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/lyh2/gstack-deepseek/tree/main/qa-only
Command: npx skills add https://github.com/lyh2/gstack-deepseek --skill qa-only-lyh2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA bottlenecks and ambiguity are reduced by a structured, report-only testing workflow that never applies changes to the codebase, ensuring visibility without modification.

Core Features & Use Cases

Systematic test execution that produces a health score, screenshots, and a reproducible report.
Generates a standalone QA report for stakeholders and mirrors the process for the full test-fix-verify loop when requested via /qa.
Works across web apps and can be invoked for smoke, regression, or exploratory testing without making changes to the app.

Quick Start

Run the qa-only workflow to perform non-fixing QA testing and generate a structured report.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is report-only QA testing and when do I need it for my web application?▼

Report-only QA testing executes a structured workflow that documents issues without applying fixes, providing visibility into web app quality through health scores and screenshots without modifying the codebase.

How do I run automated smoke and regression testing without changing my codebase?▼

Run an automated report-only QA workflow to execute smoke, regression, or exploratory testing on web applications, which generates a structured report with evidence like health scores and screenshots while never applying changes.

Can I use this report-only QA workflow across different web app stacks?▼

Yes, the report-only QA workflow works across web applications of various stacks, enabling systematic test execution that produces reproducible reports and health scores regardless of the underlying technology.

Does report-only QA testing replace the full test-fix-verify flow?▼

No, report-only QA testing documents issues without applying fixes, but it guides users toward the full test-fix-verify flow when requested via /qa to complete the lifecycle.

What's the best way to generate a standalone QA report for stakeholders?▼

Use a report-only QA workflow to produce a standalone, structured report containing health scores and screenshots, ensuring stakeholders get reproducible evidence without any codebase modifications.

Why does my QA process create bottlenecks and how can structured reporting help?▼

QA bottlenecks and ambiguity are reduced by a structured, report-only testing workflow that systematically documents issues with evidence, ensuring clear visibility and reproducible reports without modification.