qa-only

Automate browser-based QA testing to discover defects and generate structured reports.

Updated Mar 22, 2026

Search Tags:#testing #reports #qa #evidence #bug-tracking #web-app

Ready to run

npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill qa-only-jm199seo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill qa-only-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web apps often suffer from defects that aren't caught until later. QA testers spend hours reproducing issues, gathering evidence, and compiling reports that are hard to reuse across teams.

Core Features & Use Cases

Automated, browser-based defect discovery without code changes
Evidence gathering: screenshots, console logs, and repro steps
Structured health-score driven reports for quick triage and handoff

Quick Start

Run the QA skill against your target URL 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 automate browser-based QA testing to find web app bugs?▼

Automated browser-based QA testing targets a given URL to discover defects without applying code changes. It navigates the application, validates behavior, and documents issues to eliminate manual reproduction efforts.

What is a structured QA report with a health score and evidence?▼

A structured QA report provides a quantified health score for quick triage alongside captured evidence like screenshots and console logs. It documents discovered defects with repro steps to facilitate handoff between testing and development teams.

Can I run QA testing on feature branches with diff-aware defect discovery?▼

Yes, the QA testing process supports diff-aware testing on feature branches. This allows you to target specific changes and validate new behavior by comparing outcomes against the baseline application state.

Does automated QA testing gather screenshots and console logs as bug evidence?▼

Yes, automated QA testing collects screenshots and console logs during execution. This gathered evidence validates behavior and provides developers with exact repro steps needed to understand and fix the reported defects.

How do I document web app issues without applying code fixes?▼

Report-only QA testing discovers and documents web app issues without applying any code fixes. It targets a URL, optionally authenticates, and generates a detailed report containing evidence and reproduction steps for developers.

Do I need authentication credentials to run browser-based QA testing on a private URL?▼

Browser-based QA testing supports optional authentication to access private URLs. Providing credentials allows the automated browser session to log in, navigate protected areas, and accurately test authenticated user workflows.