qa-only

Automate browser-based QA testing and generate structured reports with evidence.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/yolopunk/jedi --skill qa-only-yolopunk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/yolopunk/jedi --skill qa-only-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications require rigorous QA documentation without introducing code changes. This Skill standardizes testing by performing browser-based exploration, collecting evidence, and emitting a reproducible report instead of applying fixes.

Core Features & Use Cases

  • Structured health-report generation with a health score, evidence, and repro steps.
  • Diff-aware or full-app exploration via the browser to surface issues before deployment.
  • Local artifact storage and export for regression analysis and traceability.

Quick Start

To start a QA run against a target URL, invoke the qa-only skill and it will produce a structured report with evidence.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate browser-based QA testing without modifying code?

Automated browser-based QA testing without code modification is achieved by exploring the web app, capturing screenshots and console logs, and generating a structured report with evidence instead of applying fixes.

What is a regression-ready baseline in QA testing?

A regression-ready baseline in QA testing is an exported artifact set containing repro steps, captured screenshots, and console logs stored locally for future traceability and regression analysis.

How do I generate structured QA health reports with evidence?

Structured QA health reports with evidence are generated by running browser exploration against a target URL, producing a health score and reproducible steps without applying code fixes.

Can I run diff-aware exploration to surface web app issues?

Diff-aware exploration can be run to surface web app issues by targeting changed areas rather than the full app, capturing console logs and screenshots to document evidence before deployment.

Does this QA testing approach store artifacts locally or in the cloud?

This QA testing approach stores artifacts locally, keeping screenshots, console logs, and exported baselines on your machine for immediate traceability and regression analysis.