qa-only

Identify and summarize QA issues with screenshots and a health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables a non-fixing QA pass that systematically tests a web application and produces a structured report with a health score, screenshots, and repro steps—without making code changes.

Core Features & Use Cases

  • Non-intrusive QA passes that verify behavior and surface defects without applying fixes.
  • Evidence-rich reports including health scores, annotated screenshots, and reproducible steps for each issue.
  • Proactive guidance to complement development, while preserving the codebase unchanged.

Quick Start

Run the /qa-only command to start a report-only QA pass on the current app, then review the generated results.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run a QA pass on a web app without modifying the codebase?

A non-fixing QA pass systematically tests a web application to identify and summarize issues, generating a structured report with repro steps and a health score while preserving the codebase unchanged.

What is a report-only QA testing approach for web applications?

Report-only QA testing surfaces defects by observing the app in a browser context, capturing annotated screenshots, and producing evidence-rich documentation without applying any code fixes.

Does QA testing require a browser context to capture screenshots and repro steps?

Yes, report-only QA testing requires a browser context to observe the web application, capture screenshots of identified issues, and generate structured reports with reproducible steps.

What's the best way to document web app issues with a health score during testing?

Running a non-fixing QA pass systematically verifies behavior and produces a structured report containing a health score, annotated screenshots, and reproducible steps for each defect found.

When should I use a non-fixing QA report instead of applying code fixes?

Use a non-fixing QA report when you need proactive guidance to complement development by highlighting problems and reproductions while preserving the codebase completely unchanged.