qa-only

Automate QA exploration of web apps and generate structured defect reports.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mulyoved/awesome-agent-ides --skill qa-only-mulyoved
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/mulyoved/awesome-agent-ides/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/mulyoved/awesome-agent-ides --skill qa-only-mulyoved

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline QA by performing report-only testing on web applications, generating a structured findings report without making any fixes or changes to the codebase.

Core Features & Use Cases

  • Automated exploratory QA: traverse critical user flows, collect evidence (screenshots, logs), and surface defects without applying fixes.
  • Structured reporting: produce a health score, clear repro steps, and a consolidated findings document for stakeholders.
  • Use cases: ideal for quick QA passes on feature branches or full app regressions, with artifact-based evidence for auditing.

Quick Start

Run a report-only QA pass on the target web app and generate a structured results report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate QA testing for a web application without modifying the codebase?

Report-only QA testing automates web application exploration by navigating user flows and capturing screenshots to surface defects without applying any code fixes. It generates a structured findings document containing a health score and repro steps for stakeholders.

What is structured health reporting in automated QA exploration?

Structured health reporting in QA exploration aggregates evidence like screenshots and logs into a consolidated document. It calculates a health score, details reproduction steps for identified defects, and provides artifact-based evidence for auditing.

Can I run regression testing on feature branches using report-only QA automation?

Yes, report-only QA automation applies to full regression of user journeys across pages, forms, and interactive components. It supports executing diffs on feature branches and collecting evidence without altering the application code.

Does automated QA testing capture screenshots and logs during web app navigation?

Automated QA testing coordinates browser automation to traverse critical flows, actively capturing screenshots and collecting logs as evidence. This artifact collection ensures that identified defects are backed by visual and systemic proof.

What is the best way to generate reproduction steps for defects found during web app testing?

Generating reproduction steps is handled by report-only QA automation, which navigates interactive components and records the exact sequence of actions that triggered a defect. The resulting structured report includes these steps alongside a health score.

Why does report-only QA testing not apply fixes to the defects it finds?

Report-only QA testing focuses strictly on identifying and documenting defects through evidence collection, leaving the codebase untouched. This separation ensures that testing remains an independent auditing process for stakeholders to review.