qa-only

Identify web app issues and report them with health scores and repro steps, without changing code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need to verify web applications without introducing changes to the codebase. This skill runs a non-fixing QA pass that documents findings, generates a structured report with a health score, and captures evidence such as screenshots and reproducible steps.

Core Features & Use Cases

  • Non-intrusive QA pass: perform checks and produce a comprehensive report without touching source code.
  • Evidence-rich output: health score, screenshots, and reproducible steps to aid debugging and audits.
  • Use Case: before a release, or when a team requests a bug report that does not modify the app.

Quick Start

Run the qa-only workflow on your target web app with the chosen scope and authentication to produce a structured QA 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 a QA test on a web application without changing the codebase?

You can run a non-intrusive QA pass to evaluate a web application and generate a structured report without modifying the source code. The process documents findings, captures screenshots, and records reproducible steps for later verification.

What is a non-fixing QA pass and when do I need it for web app testing?

A non-fixing QA pass is a testing process that identifies and reports issues in a web application without making code changes. Teams need this before a release or when requesting a bug report that does not modify the app.

How do I generate a bug report with health scores and screenshots for a web app?

To generate a bug report with health scores and screenshots, run a report-only QA workflow on your target web app. It produces evidence-rich output including health scoring, screenshots, and reproducible steps to aid debugging and audits.

Can I scope QA automation tests to specific diffs instead of the full application?

Yes, report-only QA automation tests are applicable to both full app and diff scopes. You can run the workflow with your chosen scope to produce a structured QA report without introducing changes to the codebase.

Does the structured QA report include reproducible steps for debugging?

Yes, the structured QA report includes reproducible steps and screenshots as evidence. This ensures that all identified issues are documented with the necessary information to aid debugging and audits.

What are the limitations of using a report-only approach for software testing?

The main limitation of this report-only approach is a strict non-fix policy; it identifies and records findings but does not modify code to resolve issues. It is designed for verification and documentation rather than automated remediation.