qa-only

Tests web applications in a browser and produces a structured QA report without fixing anything.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill qa-only-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/westkite1201/garden-engine --skill qa-only-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a web application actually works after shipping code requires tedious manual clicking, form filling, and console checking. This Skill automates report-only QA testing: it drives a real browser through your app, captures screenshots and console errors, and produces a structured report with a health score and repro steps — while never modifying any code. ## Core Features & Use Cases - Diff-aware testing: On a feature branch with no URL given, it analyzes the git diff, identifies affected pages and routes, detects the running local app, and tests exactly what changed. - Multiple modes: Full systematic exploration, 30-second quick smoke tests, and regression mode that diffs results against a saved baseline.json. - Evidence-based reporting: Every issue gets annotated screenshots, repro steps, severity classification, and a weighted health score across console, links, visual, functional, UX, performance, content, and accessibility categories. - Use Case: You just pushed a branch changing the checkout flow. Run the skill and it finds your local dev server, walks the checkout end-to-end, screenshots a broken submit button, and hands you a report — without touching your code. ## Quick Start Ask the AI to run report-only QA on your current feature branch or a specific URL such as http://localhost:3000 and produce a bug report 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 QA test my web app without fixing the bugs found?

Invoke the skill with a target URL or on a feature branch and it runs report-only testing. It clicks through pages, fills forms, captures screenshots and console errors, then writes a structured report with repro steps while never changing any code.

How does diff-aware QA testing work on a feature branch?

It analyzes the git diff between your branch and main, maps changed files to affected pages and routes, detects a running local dev server on common ports, and tests each affected page end-to-end with screenshots.

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

qa-only is report-only: it tests and documents bugs but never fixes anything. The full /qa skill runs the complete test-fix-verify loop, applying fixes and re-verifying them.

Can I run regression testing against a previous QA baseline?

Yes, pass --regression with a baseline.json from a prior run. It executes a full test pass, then diffs results to show fixed issues, new issues, and the health score delta appended to the report.

Does browser-based QA testing work with Next.js or Rails apps?

Yes, it includes framework-specific guidance: hydration error checks and client-side navigation testing for Next.js, CSRF and Turbo verification for Rails, plugin conflict detection for WordPress, and history handling for SPAs.

Why does the QA skill need a one-time browse binary setup?

The browser automation relies on a compiled browse binary that must be built once, taking about ten seconds. If bun is missing it is installed first, after which all subsequent runs use the cached binary.