qa-only

Run deterministic QA tests on web applications and generate structured health reports.

2|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vnmoorthy/Skylog --skill qa-only-vnmoorthy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/vnmoorthy/Skylog --skill qa-only-vnmoorthy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing helps teams obtain objective quality assessments without introducing changes to the codebase, delivering structured health reports, screenshots, and reproducible steps to guide improvements.

Core Features & Use Cases

  • Deterministic, report-only QA runs that generate a health score, visual evidence, and reproducible steps.
  • Supports web applications and multi-environment scenarios, without modifying code.
  • Ideal for external QA requests, audits, or bug triage where fixes are deferred.

Quick Start

Run the qa-only skill to generate a fresh test report for the current web app session.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run deterministic QA tests on a web app without modifying code?

Automated QA reporting without code modification is done by running read-only tests against a web app. This generates a structured report with a health score, screenshots, and reproducible steps.

What is a web application health score and how does it help with bug triage?

A web application health score is a metric generated by running deterministic QA tests. It provides an objective quality assessment for bug triage, helping teams prioritize fixes using structured reports and visual evidence rather than modifying the codebase.

How do I generate reproducible steps for a bug report during an audit?

To generate reproducible steps for a bug report, run a report-only QA test on your web application. The test captures objective issues and outputs a formal QA narrative containing exact reproduction steps, screenshots, and a health score for audit purposes.

Can I use automated QA testing across multiple environments without deploying fixes?

Yes, you can run report-only QA testing across multiple environments without deploying fixes. This approach requires only read access to the app under test, allowing you to obtain objective test results and structured reports without altering the codebase.

Does report-only QA testing require write access to the application under test?

No, report-only QA testing does not require write access to the application under test. It strictly requires read access to identify issues, using allowed tools like Bash and WebSearch to produce a consumable report without changing code.

Why choose report-only QA testing over automated test frameworks that fix code?

Report-only QA testing is chosen when you need objective test results without code changes. It is ideal for external audits or bug triage where fixes are deferred, delivering a formal QA narrative with visual evidence rather than modifying the codebase.