qa-only

Run automated QA tests on web applications and generate detailed reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines QA testing for web applications by automatically running tests, providing detailed reports, and generating screenshots without making any changes.

Core Features & Use Cases

  • Automated Testing: Systematically tests web applications with a focus on reporting issues.
  • Structured Reporting: Provides health scores, screenshots, and repro steps for each test.
  • Use Case: Use this Skill to get a comprehensive report on the quality of a new feature before release.

Quick Start

Run the qa-only skill to test your 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 automate QA testing for a web application to generate a bug report?

Automated QA testing executes test workflows on web applications to generate a detailed report containing health scores, screenshots, and reproduction steps for bug reporting. It focuses on producing evidence of issues without making any code fixes.

Can I use automated testing to verify UI workflows before a feature release?

Automated testing verifies web application UI workflows before a feature release by utilizing web browsing tools to capture screenshots and produce a comprehensive report on the quality of the new feature.

What is the best way to perform exploratory testing without modifying the application?

Exploratory testing without modifications runs automated tests strictly to report issues, providing structured evidence like health scores and reproduction steps without applying any fixes or making changes to the web application.

Does QA reporting provide reproduction steps and screenshots for found issues?

QA reporting provides structured evidence for found issues, generating detailed reports that include health scores, screenshots, and reproduction steps to document the quality and behavior of the web application.

Why does automated testing focus on reporting rather than fixing issues?

Automated testing focuses on reporting rather than fixing to preserve the original application state for exploratory testing and accurate bug reporting. It systematically documents issues with health scores and screenshots without applying fixes.