qa-only

Identify web application issues via report-only QA testing and generate structured bug reports.

5|2|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/agatx/serenada --skill qa-only-agatx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/agatx/serenada --skill qa-only-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend hours clicking through apps, collecting screenshots, logs, and repro steps, and producing reports that miss issues or lack consistency. This Skill standardizes and automates report-only testing to surface defects without code changes.

Core Features & Use Cases

  • Systematic, report-only testing that documents health score, screenshots, and repro steps.
  • Diff-aware analysis on feature branches and browser-based exploration to surface UI/console issues.
  • Generates a structured QA report and cross-session evidence for audits or handoffs.

Quick Start

Start a QA run on the target project to generate a standardized report with health score and evidence.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate QA testing and generate a structured bug report for a web app?

You can automate QA testing by running a report-only analysis on your web application to generate a standardized bug report. The output includes a health score, screenshots, and reproduction steps to document issues without implementing code fixes.

What is diff-aware QA testing and when do I need it for feature branches?

Diff-aware QA testing analyzes only the changed code in feature branches to surface UI and console issues. You need it to streamline regression testing and focus coverage on new interactions without scanning the entire application.

Do I need a specific QA environment to run browser-based exploration and collect screenshots?

Yes, you need a QA environment to run browser-based exploration and collect screenshots. The testing process also relies on local tooling like the browse binary and access to test-plan sources to guide coverage.

Does report-only QA testing implement code fixes for the defects it finds?

No, report-only QA testing does not implement code fixes for found defects. It strictly identifies issues across pages and interactions to produce a structured report with evidence like console logs and screenshots.

What's the best way to collect cross-session evidence for QA audits and handoffs?

The best way to collect cross-session evidence for audits is to run a standardized QA testing session that captures screenshots, console logs, and reproduction steps. This generates a structured report for consistent handoffs.