qa-only

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill qa-only-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill qa-only-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? When you want to know what is broken in your web app without changing any code, this Skill systematically tests the application like a real user and delivers an evidence-backed bug report with a health score, screenshots, and reproduction steps. ## Core Features & Use Cases - Report-only QA testing: Clicks through pages, fills forms, checks console errors, and documents issues with screenshot evidence, but never edits source code or suggests fixes. - Multiple test modes: Diff-aware mode for feature branches, full systematic exploration, 30-second quick smoke tests, and regression comparison against a saved baseline. - Structured health scoring: Computes a weighted 0-100 health score across console, links, visual, functional, UX, performance, content, and accessibility categories. - Use Case: You just pushed a feature branch and want to verify it works before merging. Run the skill with no URL and it auto-detects your local dev server, tests the pages affected by your diff, and writes a report to .gstack/qa-reports/. ## Quick Start Ask the assistant to run a report-only QA pass on your local app at localhost:3000 and save the bug report with screenshots.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I get a bug report for my web app without fixing anything?

Run the qa-only skill with your app URL or on a feature branch. It navigates pages, tests forms and interactions, captures screenshots, and writes a structured report with a health score to .gstack/qa-reports/ without touching source code.

What is the difference between qa-only and the qa skill?

qa-only is report-only: it finds and documents bugs but never fixes them or reads source code. The qa skill runs the full test-fix-verify loop, so use qa when you want issues repaired and qa-only when you just want a report.

Can I run QA testing on a feature branch without a URL?

Yes. On a feature branch with no URL, the skill enters diff-aware mode: it analyzes the git diff, identifies affected pages and routes, auto-detects a local dev server on common ports, and tests only what changed.

Does the QA report support regression comparison?

Yes. Pass a baseline.json from a previous run with the regression flag. The skill diffs current results against the baseline, reporting fixed issues, new issues, and the health score delta.

Why does the browse setup fail on first run?

The browse binary needs a one-time build that requires bun. If bun is missing, the skill installs it with a checksum-verified script, then runs the setup script in the skill directory before any browser command.