qa-only

Identify and report web app defects with reproducible steps and screenshots without altering code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA verification and defect reporting for web applications, without attempting fixes, to accelerate triage and documentation.

Core Features & Use Cases

  • Systematic exploratory QA passes that log health scores, reproduce steps, and evidence (screenshots) for each issue.
  • Structured, shareable QA reports that highlight regressions, unexpected behavior, and risk areas.
  • Use case: When a bug is found, generate a detailed report with steps to reproduce and expected vs actual outcomes, without altering the codebase.

Quick Start

Run a complete QA pass against the target web app and generate a structured report including health scores, evidence, and repro 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 a QA report with repro steps and screenshots for a web app?

Run a complete exploratory QA pass against your web application to systematically identify defects, capture screenshots, and log reproducible steps. This produces a structured health report with evidence, avoiding any code changes or fixes unless explicitly requested.

Can I document web application bugs without applying code fixes?

Yes, you can document web application bugs without applying fixes. The skill identifies and reports defects across user flows, forms, and navigation, producing structured bug reports with screenshots and repro steps while explicitly avoiding any codebase changes unless requested.

What is the best way to document unexpected behavior and risk areas during web app testing?

The best way to document unexpected behavior is to run systematic exploratory QA passes. This generates a structured, shareable report highlighting regressions, unexpected visual behaviors, and risk areas, complete with health scores and screenshot evidence for triage.

Does automated QA testing work for validating common user flows and forms?

Automated QA testing works for validating common user flows, forms, and navigation. It targets these specific behaviors to identify unexpected issues, capturing outcomes and visual evidence to generate a comprehensive health report for your web application.

How do I capture expected vs actual outcomes when reproducing a bug?

To capture expected versus actual outcomes when reproducing a bug, execute the reproducible steps during your QA pass. The system logs these outcomes alongside screenshots in a structured report, providing clear documentation for triage and regression tracking.