qa-only

Run read-only QA checks on web applications and generate structured bug reports.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill qa-only-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill qa-only-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA web applications by identifying defects and generating a structured report, without making any changes to code or deployments.

Core Features & Use Cases

  • Read-only testing: Executes QA checks without modifying source or environments.
  • Structured reports: Produces a health score, includes screenshots, and lists clear repro steps.
  • Triage-ready outputs: Summarizes findings in a format suitable for engineering teams and QA leads.

Quick Start

Run a read-only QA pass on the target app and generate a 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 automate read-only QA testing for a web application?

Read-only QA testing executes regression checks without modifying code or deployments. It systematically identifies defects across UI and API surfaces, recording screenshots and concise findings to guide triage and verification.

What is a structured bug report with health scoring and repro steps?

A structured bug report compiles QA findings into a health score, includes screenshots, and lists clear reproducible steps. This format summarizes defects in a triage-ready output suitable for engineering teams and QA leads.

Can I run regression checks on both UI and API surfaces without applying fixes?

Yes, regression checks can target both UI and API surfaces while remaining strictly report-only. The process executes read-only testing to identify defects and generates a bug report without making any changes to source code or environments.

What's the best way to generate triage-ready bug reports from web app testing?

Generating triage-ready bug reports requires running a read-only QA pass that produces a health score, captures screenshots, and lists clear repro steps. This format summarizes findings to directly guide engineering teams during triage and verification.

Does read-only QA testing modify my source code or deployment environments?

No, read-only QA testing does not modify your source code or deployment environments. It executes checks strictly to identify defects and compile a structured report, ensuring the application remains unchanged during the testing process.