qa-only

Test web applications and generate structured bug reports with health scores.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill qa-only-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/yocxy2/gstack3/tree/main/qa-only
Command: npx skills add https://github.com/yocxy2/gstack3 --skill qa-only-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the need for objective, non-intrusive quality assurance by performing comprehensive web application testing and generating detailed bug reports without modifying any source code.

Core Features & Use Cases

  • Automated Reporting: Generates structured reports including health scores, screenshots, and clear reproduction steps.
  • Non-Destructive Testing: Validates application behavior and identifies regressions while strictly adhering to a read-only policy.
  • Use Case: Use this when you need to verify a production deployment or investigate a reported issue without risking accidental code changes or side effects.

Quick Start

Invoke the qa-only skill to perform a full diagnostic test on the current web application and generate a bug report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I perform read-only web testing without modifying source code?

Read-only web testing executes test suites to capture diagnostic data and generate bug reports without modifying source code. It validates application behavior and identifies regressions while preventing accidental side effects to production deployments.

What is a structured bug report with health scores for web applications?

A structured bug report includes health scores, screenshots, and clear reproduction steps to document web application issues. It provides objective quality assurance by capturing diagnostic data during automated testing sessions.

Can I verify a production deployment using automated browser testing safely?

Verifying a production deployment with automated browser testing is safe when using a read-only policy. It executes test suites to investigate reported issues and capture diagnostic data without risking accidental code changes or side effects.

Do I need Bash and web access to run automated web testing for bug reports?

Automated web testing requires Bash, web access, and standard browser automation tools to execute test suites and capture diagnostic data. These dependencies are necessary to generate structured bug reports with health scores and reproduction steps.

What are the limitations of non-destructive QA testing?

Non-destructive QA testing is limited to read-only verification and cannot modify source code or fix identified bugs. It strictly adheres to a read-only policy to ensure no code changes occur during the verification process.