qa-only

Analyze a web application with report-only tests and produce a structured bug report.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill qa-only-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/lemig/transcriptor --skill qa-only-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA-only analyzes a web application by performing report-only tests and producing a structured bug report.

Core Features & Use Cases

  • Reports health score, reproducible steps, and evidence (screenshots) without applying fixes.
  • Supports both manual and automated QA passes to surface issues efficiently.
  • Use Case: when you need a comprehensive QA snapshot for a release candidate without altering code.

Quick Start

Ask the QA-only skill to generate a test report for the current web app without making any changes.

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 bug report for a web app without modifying the code?

Report-only QA testing generates a structured bug report for web apps without modifying code. It produces a health score, reproducible steps, and screenshot evidence by running manual or automated checks while strictly avoiding fixes.

What is included in a report-only QA testing snapshot?

A report-only QA testing snapshot includes a web app health score, detailed repro steps, and screenshot evidence. It surfaces issues found during manual checks or automated passes within a structured bug report.

Can I run automated QA passes on a release candidate without altering the source?

Yes, automated QA passes can run on a release candidate without altering the source. The process analyzes the web app and produces a comprehensive QA snapshot in a structured bug report, ensuring no code is modified.

Do I need external services to capture screenshots and repro steps for a bug report?

No external services are needed to capture screenshots and repro steps. The testing process relies solely on its internal toolset to generate the structured bug report, health score, and evidence.

When should I use a report-only testing approach instead of applying fixes?

Use a report-only testing approach when you need a comprehensive QA snapshot for a release candidate. It is designed for safety when you require health scores and reproducible steps without modifying existing code.