qa-only

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

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/rshelekhov/dotfiles --skill qa-only-rshelekhov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/rshelekhov/dotfiles/tree/main/claude/skills/gstack/qa-only
Command: npx skills add https://github.com/rshelekhov/dotfiles --skill qa-only-rshelekhov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing systematically checks a web application and outputs a structured report with a health score, evidence, and reproducible steps — but never applies fixes.

Core Features & Use Cases

  • Systematic QA passes that simulate real user interactions and generate a health-score report.
  • Evidence & Repro: auto-generated screenshots, logs, and steps to reproduce for every issue.
  • No-fix policy: captures and documents bugs without applying changes to the code.
  • Use cases: when you want documented QA results before release, for audits, or when asked to "just report bugs" or "qa report only".

Quick Start

Ask me to run /qa on your web app to generate a report-only QA pass.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run report-only QA testing on a web application without modifying code?

Report-only QA testing systematically checks a web application and generates a structured report with health scores, evidence, and reproducible steps without applying any code fixes.

What is included in an automated web application QA report?

An automated QA report includes a health score, auto-generated screenshots, logs, and exact steps to reproduce for every documented issue found during the test pass.

Can I use this for a bug audit before a software release?

Yes, this approach is applicable for pre-release documentation, bug audits, and generating health snapshots by simulating user interactions and collecting evidence without altering the codebase.

How do I document bugs with reproducible steps and screenshots automatically?

Automated report-only QA captures and documents bugs by generating structured outputs that contain screenshots, logs, and exact steps to reproduce for every issue encountered.

Does report-only QA testing apply fixes to the codebase?

No, report-only QA testing enforces a strict no-fix policy that captures and documents bugs with evidence and health scores while avoiding any changes to the application code.

What is the best way to get a documented health snapshot of a web application?

Running an automated report-only QA pass simulates real user interactions to produce a structured health snapshot, complete with evidence and reproducible steps for identified issues.