qa-only

Name: qa-only
Availability: InStock
Author: forbotsake

Identify web application defects through manual-style QA checks and structured reports.

5|1|Updated Apr 5, 2026

Search Tags:#testing #qa #evidence #web-app #bug-report #manual-testing #repro-steps

Ready to run

npx skills add https://github.com/forbotsake/forbotsake --skill qa-only-forbotsake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/forbotsake/forbotsake/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/forbotsake/forbotsake --skill qa-only-forbotsake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing often requires risky changes to demonstrate issues. This skill performs thorough manual-style checks on a web application and compiles a structured report with evidence, but it never makes changes to the codebase.

Core Features & Use Cases

Manual-style exploration: Click through the app, fill forms, verify state changes, and capture evidence.
Structured report: Generates a reproducible report with health indicators, screenshots, and step-by-step repro notes.
No-fix policy: Limits itself to reporting; it does not modify code or deploy patches, fitting workflows that require validation before any changes.
Use Case: Run a full regression on a login flow and produce a report you can hand to engineering for triage.

Quick Start

Provide a target URL and let the QA-only workflow generate a test 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 manual-style QA checks on a web app without modifying the codebase?▼

Manual-style QA checks can be performed by simulating user actions like clicking and filling forms on a running web app, capturing evidence such as screenshots and repro steps, and compiling a structured report without applying any code fixes.

What is a report-only QA workflow and when do I need it for web application testing?▼

A report-only QA workflow identifies defects through full-regression, smoke, or targeted diff checks and produces a structured report with health indicators. It is needed when validation must occur before any engineering changes are authorized.

How do I generate a structured bug report with screenshots and repro steps for a web application?▼

To generate a structured bug report, simulate user interactions on the target URL, capture screenshots of defects, document step-by-step reproduction notes, and compile them into a report with health indicators for engineering triage.

Can I perform a full regression test on a login flow and produce a report for engineering triage?▼

Yes, you can perform a full regression test on a login flow by simulating authentication and page interactions, verifying state changes, and handing the resulting structured report with evidence directly to engineering for triage.

Does report-only testing actually fix bugs found during web application smoke checks?▼

No, report-only testing enforces a strict no-fix policy. It limits itself to identifying defects during smoke checks and compiling evidence, intentionally avoiding any code modifications or patch deployments.

What is the best way to document web application defects without deploying automated fixes?▼

The best way to document defects without deploying fixes is to perform manual-style exploration, capture screenshots and reproducible steps, and compile a structured validation report that separates testing evidence from codebase changes.