qa-only

Run report-only QA testing on web applications and generate verification reports.

48|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/g4rcez/dotfiles --skill qa-only-g4rcez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/qa-only
Command: npx skills add https://github.com/g4rcez/dotfiles --skill qa-only-g4rcez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing to verify a web application without applying fixes, producing a structured, evidence-backed report.

Core Features & Use Cases

  • Systematic, no-fix QA passes for new builds or deployments
  • Generates health scores, screenshots, and a reproducible steps log
  • Useful when you need formal QA validation before release or handoff

Quick Start

Run a report-only QA pass on the target app and generate a structured verification report with health score, evidence screenshots, and reproducible 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 QA testing on a web build and automatically capture bug evidence with screenshots?

Report-only QA testing automates build-by-build verification by systematically assessing web application health, capturing evidence screenshots, and generating a reproducible steps log without applying fixes.

What is report-only QA testing and when do I need it for my deployment process?

Report-only QA testing verifies a web application without making code changes, producing a structured, evidence-backed report needed for formal validation before release or handoff.

How do I generate a structured QA report with a health score and reproducible steps?

Generate a structured verification report by running an automated QA pass that targets your web application, calculates a health score, captures screenshots, and logs reproducible steps.

Does QA testing work without applying fixes to verify a new build?

Yes, report-only QA testing verifies new builds systematically without applying any fixes, strictly defining inputs, outputs, and constraints using Bash, Read, Write, and AskUserQuestion tools.

What's the best way to perform a no-fix verification pass for formal release validation?

The best way is report-only QA testing, which performs a systematic health assessment and produces evidence-backed reports with screenshots and repro logs, leaving the application untouched.