qa-only

Generate report-only QA findings with screenshots and a health score.

6|2|Updated Oct 18, 2021
One-click install
npx skills add https://github.com/jerrywu001/jerrywu001 --skill qa-only-jerrywu001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill qa-only-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

qa-only helps you verify a web application behaves correctly by systematically testing user-facing flows and producing clear evidence, while explicitly never making any changes to fix issues.

Core Features & Use Cases

  • Structured QA report: Generates a health score, categorized issues, and screenshots for proof of what was broken.
  • Repro steps with evidence: Captures before/after states for interactive failures so bugs can be investigated efficiently.
  • Safe “report-only” mode: Thoroughly tests pages and interactions without attempting fixes, ideal for “just report” requests.
  • Use case: You want a clean bug report after a release or during a manual QA cycle, and you need screenshot-backed findings for engineers.

Quick Start

Ask for a report-only QA run by saying: run qa-only against https://your-app.com and produce a structured bug report with screenshots and repro steps, without fixing anything.

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 bug report for a web application without modifying any code?

To generate a bug report without modifying code, you can run a report-only QA testing session against your web application to explore pages, interact with UI elements, and collect screenshot evidence. This process systematically captures repro steps and console errors while explicitly avoiding any code changes.

Can I perform regression testing and get a structured health score for my web app?

Yes, you can perform regression testing by running a report-only QA session to evaluate your web app and generate a structured health score. This approach systematically explores user-facing flows and produces categorized findings with screenshot-backed evidence for stakeholder handoffs.

What is the best way to capture UI interaction failures with screenshots for QA testing?

The best way to capture UI interaction failures is to run a QA testing session that records before and after states during web application exploration. This generates a structured bug report containing screenshot and console evidence, ensuring interactive failures are documented with clear repro steps.

Does browser automation QA testing support authentication and URL selection when testing web applications?

Browser automation QA testing optionally supports authentication and diff-aware selection when URL input is omitted during web application testing. This allows the automated session to access protected pages and systematically interact with UI elements to produce a structured health score and bug findings.

Why should I use a report-only QA approach for manual QA cycles and stakeholder handoffs?

You should use a report-only QA approach to ensure thorough testing of web application pages without attempting fixes, which is ideal for manual QA cycles. It produces a clean bug report with screenshot-backed findings and a health score, providing engineers with safe, structured evidence for stakeholder handoffs.