qa-only

Execute report-only QA tests on a web application and generate a health score, screenshots, and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing to identify defects without applying fixes.

Core Features & Use Cases

  • Structured QA passes that generate a health score, screenshots, and reproducible repro steps without modifying code or deployments.
  • Suitable for full regression or targeted page checks, enabling quick triage and documentation for stakeholders.
  • Use case: you want a quick, thorough quality check before a release and need a clear report for bug triage.

Quick Start

Run a report-only QA pass on the target site and review the resulting health score, screenshots, and repro steps.

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 report-only QA test on a web application?

Report-only QA testing executes test passes on a web application to identify defects and generates a health score, screenshots, and reproducible steps without applying fixes or modifying code.

What is a health score in web app QA reporting?

A health score in QA reporting quantifies the overall quality of a web application after a test pass, summarizing identified defects alongside screenshots and repro steps for stakeholder triage.

Can I use report-only QA testing for a full regression pass?

Yes, report-only QA testing supports both full regression passes and targeted page checks, validating test coverage and compiling a structured report without deployments.

Does report-only QA testing modify my code or trigger deployments?

No, report-only QA testing strictly avoids code changes and deployments, focusing entirely on defect identification, test coverage validation, and structured report compilation.

What is the best way to document reproducible steps for bug triage before a release?

Executing a report-only QA pass is the best way to document reproducible steps, generating a structured report with screenshots and a health score for quick bug triage before release.

When should I not use a report-only approach for QA testing?

You should not use report-only QA testing when you need to automatically apply fixes or deploy code changes, as this workflow strictly executes tests and compiles reports without modifying the application.