qa-only

Tests web applications in a browser and produces structured QA reports without fixing code.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill qa-only-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack/qa-only
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill qa-only-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, and includes references (resource) components.

What problem does it solve? Verifying that a web app actually works after shipping code usually means manual clicking, screenshotting, and note-taking. This Skill automates report-only QA: it drives a real browser through your app, documents bugs with evidence, and computes a health score, while never touching your code. ## Core Features & Use Cases - Diff-aware testing: On a feature branch with no URL given, it analyzes the git diff, maps changed files to affected pages and routes, and verifies the branch's changes end-to-end in a browser. - Structured bug reports: Every issue gets screenshots, repro steps, severity, and category, written to .gstack/qa-reports/ using a report template, plus a weighted health score across console, links, visual, functional, UX, performance, and content. - Multiple modes: Full systematic exploration, 30-second --quick smoke test, and --regression mode that diffs results against a saved baseline.json to show fixed issues, new issues, and score delta. - Use Case: You just pushed a branch changing the checkout flow. Run the skill with no arguments; it detects your local dev server, tests the affected pages, and hands you a report with screenshots proving what works and what broke. ## Quick Start Ask the AI to run /qa-only on your current feature branch or against a URL like http://localhost:3000 and produce a bug report without changing any code.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I QA test my web app without fixing the bugs found?

Run the qa-only skill against your URL or feature branch. It explores the app in a browser, documents each issue with screenshots and repro steps, computes a health score, and writes a report to .gstack/qa-reports/ without ever modifying code.

How do I test only the pages changed on my feature branch?

Invoke the skill with no URL while on a feature branch. It enters diff-aware mode, runs git diff against main, maps changed files to affected routes and pages, detects your local dev server, and tests only what the branch touched.

Can I compare QA results against a previous test run?

Yes, use --regression with a baseline.json from a prior run. The skill runs a full test, then diffs the results to show which issues were fixed, which are new, and how the health score changed.

Does browser QA testing work with login-protected pages?

Yes. The skill supports filling login forms with provided credentials or importing a cookies.json file. For 2FA it asks you for the code, and for CAPTCHAs it pauses so you can complete the challenge manually.

Why does the browse setup fail on first run?

The browse binary needs a one-time build that takes about 10 seconds. If bun is missing, the skill installs it via the official bun.sh installer, then runs the setup script in the skill directory before testing.