qa

Automate end-to-end web application QA testing with tiered verification and structured reports.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill qa-jm199seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill qa-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers spend cycles validating apps, reproducing bugs, and verifying fixes; this Skill orchestrates systematic QA testing and rapid, atomic bug fixes to ship with confidence.

Core Features & Use Cases

  • Systematic QA passes with Quick, Standard, and Exhaustive tiers to match risk and time constraints.
  • Generates before/after health scores, evidence, and a ship-readiness summary to accompany releases.
  • Records actionable test artifacts and can re-run verification after fixes to confirm regressions are addressed.

Quick Start

Invoke the QA workflow on your app by issuing /qa with a target URL and a tier.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end web application testing and bug reproduction?

Automated QA orchestration executes deterministic steps against a target URL to reproduce bugs, apply atomic code fixes, and re-verify regressions. It generates structured telemetry reports and a ship readiness assessment across Quick, Standard, and Exhaustive tiers.

What is the best way to verify bug fixes without introducing regressions in a web app?

Iterative QA workflows verify bug fixes by applying atomic code changes and re-running deterministic test steps. This process records actionable test artifacts and confirms that regressions are addressed before producing a final ship readiness summary.

How do I generate ship readiness reports with health scores for my web application?

Ship readiness reports are generated by running systematic QA passes that calculate before and after health scores. These passes collect evidence and telemetry to produce a structured summary accompanying your release.

Do I need a specific environment setup to run telemetry-enabled QA automation?

Telemetry-enabled QA automation requires a test-enabled environment to execute deterministic steps and version-controlled commits. This setup allows the workflow to reproduce bugs accurately and apply iterative fixes atomic to the codebase.

How do I choose between Quick, Standard, and Exhaustive QA testing tiers?

Quick, Standard, and Exhaustive QA testing tiers match varying risk and time constraints. Selecting a tier determines the depth of systematic QA passes, balancing thorough bug validation and telemetry reporting against execution time.