qa-only

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

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill qa-only-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-qa-only
Command: npx skills add https://github.com/drt0927/tw-overlay --skill qa-only-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often need testing without making changes to the codebase. This Skill runs non-intrusive checks and returns a structured report including a health score, screenshots, and reproducible steps, without applying fixes.

Core Features & Use Cases

  • Non-intrusive web app testing that documents findings with a health score and repro steps
  • Automated screenshot capture and structured reports for review
  • Guided prompts when asked to "just report bugs" or "qa report only", or to use the full test-fix-verify loop with /qa

Quick Start

Instruct it to run the QA report on your target web application and review the generated output.

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 my web app without modifying the codebase?

Report-only QA testing allows you to run non-intrusive checks on a web application that generate a structured health report and screenshots without applying fixes. This approach strictly preserves your code base integrity while documenting findings.

What is included in an automated web app health report?

An automated web app health report includes a calculated health score, captured screenshots, and detailed reproduction steps. This structured output provides auditable results for QA teams to review.

How do I generate bug reproduction steps for a web application automatically?

Automated report-only QA testing generates bug reproduction steps by running a deterministic workflow on your web application. It documents findings and outputs reproducible steps without modifying code.

Can I use this QA testing approach if I only need to document bugs and not fix them?

Yes, report-only QA testing is designed for exactly this scenario. You can trigger it by instructing a tool to just report bugs or run a qa report only, ensuring it documents findings without applying fixes.

What is the difference between a report-only QA test and a full test-fix-verify loop?

Report-only QA testing strictly documents findings with screenshots and reproduction steps without touching the codebase. A full test-fix-verify loop uses the same guided workflow but proceeds to apply fixes and verify the results.

Does report-only QA testing capture screenshots automatically?

Yes, report-only QA testing features automated screenshot capture during its checks. It generates structured health reports that include these screenshots and reproduction steps for later review.