qa-only

Identify and report QA findings for web applications without applying fixes.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill qa-only-omerfarukoruc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/OmerFarukOruc/symphony-orchestrator/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill qa-only-omerfarukoruc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing is automated and structured, surfacing issues without applying fixes. It helps teams validate behavior and generate reproducible evidence before integration.

Core Features & Use Cases

  • Systematic QA runs that produce a health score, screenshots, and repro steps.
  • Non-intrusive testing: analyses app state and areas of risk without code changes.
  • Use cases include quick sanity checks on new features, regression vetting, and stakeholder reporting.

Quick Start

Prompt the agent to run a report-only QA pass on the target URL and return a structured findings report without making any code changes.

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 tests on a web application without making code changes?

Report-only QA testing analyzes a web application without applying fixes, safely surfacing issues across development, staging, or production-like environments. It produces a structured findings report with a health score, screenshots, and repro steps for human review.

Can I generate bug reports with repro steps for ad-hoc web testing?

Yes, you can generate structured bug reports containing evidence like screenshots and detailed repro steps. This supports exploratory testing and ad-hoc bug reporting by capturing reproducible evidence of application behavior before integration.

What is the best way to perform regression checks before integration?

Performing non-intrusive report-only QA runs is an effective way to vet regressions before integration. It systematically analyzes app state and areas of risk, outputting a health score and structured findings report without modifying your codebase.

Does report-only testing work for staging and production-like environments?

Report-only testing works across development, staging, and production-like environments. It systematically analyzes the application state and risk areas without code changes, making it safe to execute sanity checks and generate stakeholder reports in live-like settings.

How do I get a structured QA report with a health score for my web app?

You can prompt the agent to run a report-only QA pass on a target URL to receive a structured findings report. The output includes a calculated health score alongside screenshots and repro steps, delivering comprehensive evidence for stakeholder review.