qa-only

Test web applications like a human user and generate structured QA reports with health scores, evidence, and repro steps.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/TobiasPerry/aws-hackathon --skill qa-only-tobiasperry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/TobiasPerry/aws-hackathon/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/TobiasPerry/aws-hackathon --skill qa-only-tobiasperry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often need to verify software quality without changing code. This skill performs report-only testing of web applications, producing a structured health score, evidence such as screenshots, and reproducible steps, while never applying fixes.

Core Features & Use Cases

  • Test-like a user across web apps and generate a structured report with health scores, evidence (screenshots), and reproducible steps without applying fixes.
  • Supports both quick smoke checks and full regression testing, adaptable to project needs.
  • Produces clear, actionable reports for stakeholders to review and triage issues.

Quick Start

Run the qa-only skill on the target URL to start a report-only QA session.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a QA report for a web application without modifying the code?

You can generate a report-only QA test for a web app by running a skill that simulates user interactions, captures screenshots and console errors, and outputs structured health scores and repro steps without applying any fixes.

Can I run automated smoke checks and full regression testing on single-page apps?

Yes, automated smoke checks and full regression testing are supported for single-page apps, multi-page flows, and forms, allowing you to scale testing from quick verification to comprehensive coverage based on project needs.

How do I capture evidence like screenshots and repro steps for bug reports?

To capture evidence for bug reports, the testing skill records screenshots, console checks, and structured reproducible steps during its test-like-a-user execution, compiling them into an actionable report for stakeholder triage.

What is the best way to test web app forms and multi-page flows like a human user?

The best way to test web app forms and multi-page flows is using a skill that mimics human user behavior, automatically generating a test plan, identifying issues, and producing a structured health score without altering the application.

Does this QA testing approach apply fixes or patches to issues it finds?

No, this QA testing approach is strictly report-only and never applies fixes or patches; it solely identifies issues, assigns health scores, and generates structured reports with evidence and repro steps for development teams to review.