qa-only

Produce report-only QA findings with screenshots, console logs, and reproducible steps.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/24601/gastack-pre-fork --skill qa-only-24601
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/24601/gastack-pre-fork/tree/main/qa-only
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill qa-only-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured, report-only QA for web applications so teams can get evidence-driven bug reports without applying any fixes. It removes the manual work of clicking through flows, capturing screenshots, checking console errors, and writing repro steps so engineers and PMs can triage quickly.

Core Features & Use Cases

  • Diff-aware testing: Scope tests to files changed on a feature branch and verify intended pages and routes.
  • Multiple modes: Full systematic exploration, quick smoke tests, and regression comparisons against a saved baseline.
  • Evidence-first reporting: Screenshots, before/after snapshots, console logs, health score, and exportable baseline JSON for CI or PR attachments.
  • Auth and flows: Supports cookie import, scripted login flows, 2FA handling prompts, and clear guidance when manual CAPTCHA or human input is required.
  • Use case: Run when a developer asks "just report bugs" on a branch or wants a non-invasive QA pass on a staging URL.

Quick Start

Ask gstack to run /qa-only against the current branch or provide a target URL to produce a report-only QA with screenshots, console logs, a health score, and reproducible steps.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate QA bug reports with screenshots and repro steps for a web application?

This Skill captures screenshots, console logs, and reproducible steps during a browser-driven web exploration, producing structured, evidence-driven QA bug reports without applying any code fixes for quick triaging.

Can I run regression testing against a saved baseline JSON for my staging site?

You can run regression testing against a saved baseline JSON by comparing current browser-driven snapshots and console logs against the baseline, producing a structured health score comparison report for the web application.

Does diff-aware testing work for checking only changed files on a feature branch?

Diff-aware testing scopes the QA process to files changed on a feature branch, verifying intended pages and routes to produce targeted report-only findings without running full site exploration.

How do I handle 2FA or CAPTCHA prompts during automated web QA exploration?

During automated web QA, the Skill supports scripted login flows and cookie imports, providing clear guidance and pausing for manual human input when CAPTCHA or 2FA intervention is required.

What is a web application health score and how is it computed during smoke testing?

Computed during web QA, a health score aggregates console error detection, navigation mapping success, and snapshot completeness into a quantifiable metric included in the exported baseline JSON report.

What is the best way to run a quick smoke test on a staging URL without applying fixes?

The best way to run a non-invasive quick smoke test on a staging URL is using a report-only QA mode that systematically captures screenshots and console errors without applying any fixes.