qa-only

Test web applications and generate structured bug reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables thorough QA testing to identify issues in a web application and generate a structured bug report without making any changes to the codebase, ensuring teams have clear, actionable feedback.

Core Features & Use Cases

  • Systematic manual testing that surfaces UI/UX issues, functional defects, and regression risks.
  • Produces detailed repro steps, evidence (screenshots), health-oriented scoring, and a comprehensive report for stakeholders.
  • Use cases include “test but don't fix” scenarios, exploratory QA, and QA report generation on demand.

Quick Start

Start a report-only QA session by launching a browser-based test and generating a structured bug report.

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 a web application to find bugs without modifying code?

Report-only QA testing systematically executes interactive web app navigation, forms, and state handling to surface UI/UX defects and regressions, producing a structured bug report without touching the codebase.

What is the best way to generate a structured bug report for a single-page application?

Generating a structured bug report for a single-page application involves performing thorough QA testing on visual correctness and functional defects, then documenting detailed repro steps and screenshots for stakeholders.

Can I use this QA testing approach for exploratory testing on demand?

Exploratory QA testing on demand is supported by launching a browser-based test session guided by a defined test plan, which observes and documents findings to generate comprehensive QA reports.

Do I need a defined test plan to perform e2e testing on a running web app?

A defined test plan or scope is required to guide coverage during e2e testing, ensuring the systematic manual testing accurately targets the running app context and surfaces relevant regressions.

What limitations exist when using a report-only QA workflow for web applications?

The report-only QA workflow is limited to observing and documenting findings, meaning it will not modify code to fix identified functional defects or regression risks; it strictly produces actionable feedback and evidence.

Does report-only testing work with interactive web apps and single-page applications?

Report-only testing applies directly to interactive web apps and single-page applications, specifically testing navigation, forms, state handling, and visual correctness to surface issues for stakeholders.