skills.rest
stayconnectquick
stayconnectquickCOMMUNITY
Explore all skills by this author →
GitHub

qa-only

Run report-only QA testing to generate health scores, screenshots, and reproducible steps.

Updated May 6, 2026
Search Tags:#automation#testing#qa#reporting#quality-assurance#web-app#bug-report
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill qa-only-stayconnectquick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/stayconnectquick/gstack/tree/main/qa-only
Command: npx skills add https://github.com/stayconnectquick/gstack --skill qa-only-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables report-only QA testing that produces a structured health score, evidence (screenshots), and reproducible steps without changing or fixing the target application.

Core Features & Use Cases

  • Non-intrusive QA passes that generate a health score, visual evidence, and step-by-step repro details for each issue.
  • Structured reporting suitable for handoffs to developers, product managers, or stakeholders to triage bugs without code changes.
  • Use cases include “just report bugs,” QA audits, regression verification without fixes, and documentation for compliance or release-readiness.

Quick Start

Ask the qa-only skill to run a report-only QA pass and generate a structured 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 run QA testing on a web app to document bugs without changing the code?▼

Report-only QA testing documents bugs without applying fixes by running nondestructive checks on your web application to generate a structured health score, screenshots, and reproducible steps for triage.

Can I generate a health score and reproducible steps for UI bugs without applying fixes?▼

Yes, you can generate a health score and step-by-step reproducible details for UI bugs without applying fixes. This report-only approach provides documented evidence for developers to triage issues.

Does report-only QA testing support both manual exploration and automated checks?▼

Report-only QA testing supports both manual exploration and automated checks for web applications and user interfaces. It requires access to the app under test and the ability to run nondestructive tests.

What is the best way to create structured bug reports for release-readiness verification?▼

Structured bug reports for release-readiness verification are best created through report-only QA passes that emit a consistent, machine-readable format with visual evidence, suitable for compliance documentation and stakeholder handoffs.

When should I use a report-only QA pass instead of a full testing and fixing workflow?▼

Use a report-only QA pass when your web application requires documented evidence of bugs for stakeholder triage or compliance rather than immediate code changes, ensuring non-intrusive regression verification without altering the target application.

Related Skills

Explore More Software Engineering Skills→
asmyshlyaev177asmyshlyaev177
418

shared-state-no-url

Share module-scoped application state across React components without URL synchronization.

Community
Basic
zhifengzhang-szzhifengzhang-sz

qa-only

Run report-only QA tests on web applications and export structured bug reports.

Community
Intermediate
manushi4manushi4
11

qa-smoke-test

Automate QA smoke tests for desktop and web apps using ScreenHand tools.

Community
Intermediate
huichenhuichen

qa-only

Automate report-only testing of web applications to generate health reports with screenshots and repro steps.

Community
Intermediate