skills.rest
legotec73
legotec73COMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-only

Generate report-only QA health scores, screenshots, and repro steps for web applications.

Updated Apr 13, 2026
Search Tags:#testing#qa#bug-report#health-score#repro-steps#non-fixing
One-click install
npx skills add https://github.com/legotec73/gstack --skill qa-only-legotec73
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/legotec73/gstack/tree/main/qa-only
Command: npx skills add https://github.com/legotec73/gstack --skill qa-only-legotec73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides report-only QA testing that systematically checks a web application and generates a structured, human-readable report with health indicators, screenshots, and repro steps, without performing any fixes.

Core Features & Use Cases

  • Systematic QA reporting: scans pages, interactions, and states to produce a health score and detailed bug repro steps.
  • Non-intrusive: does not modify code or deploy fixes; focuses on detection and documentation.
  • Use Case: run a non-fixing QA pass across a new release and generate a conclusive Bug Report with health metrics for stakeholders.

Quick Start

Run a report-only QA pass on the target site and review the findings in the output directory.

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 application without modifying the code?▼

Report-only QA testing systematically scans web application pages and interactions to identify defects without applying fixes. It generates structured health scores, screenshots, and repro steps for audit-ready reports across release cycles.

What is a non-fixing QA pass and when do I need it for a release cycle?▼

A non-fixing QA pass detects and documents web application defects without modifying code. You need it when generating conclusive bug reports with health metrics and repro steps for stakeholders before applying any fixes.

Can I generate structured bug reports with repro steps and health scores for web applications?▼

Yes, you can generate structured bug reports containing health scores, screenshots, and detailed repro steps. This report-only QA process systematically checks web application states to produce audit-ready documentation.

Does report-only QA testing work for generating audit-ready reports across release cycles?▼

Report-only QA testing works across release cycles by scanning pages, interactions, and states to produce structured health indicators and repro steps. It enforces a non-fixing policy for conclusive, audit-ready stakeholder reports.

What are the limitations of using a non-fixing QA approach for web testing?▼

The limitation of a non-fixing QA approach is that it strictly detects and documents defects without applying any code fixes or modifications. It focuses solely on generating health scores, screenshots, and repro steps for reporting purposes.

Related Skills

Explore More Software Engineering Skills→
edwardmonteiroedwardmonteiro

optimization.quality_report

Generate recurring quality reports synthesizing defect trends, automation health, and recommendations.

Community
Basic
GrassHopper42GrassHopper42

qa-only

Conducts systematic QA web app testing and generates structured health-score reports with screenshots and repro steps.

Community
Intermediate
aporto-techaporto-tech

Qa Only

Generate QA reports with health scores and screenshots for web applications.

Official
Advanced
huichenhuichen

qa-only

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

Community
Intermediate