qa-only

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

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill qa-only-bobbo01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-qa-only
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill qa-only-bobbo01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that a web app actually works after shipping code is tedious manual clicking. This Skill systematically tests a web application like a real user and produces a structured QA report with a health score, screenshots, and reproduction steps, while never modifying any code. ## Core Features & Use Cases - Report-only testing: Explores pages, clicks elements, fills forms, and documents issues with screenshot evidence, but never fixes anything. - Multiple modes: Diff-aware mode scopes testing to files changed on a feature branch; full mode explores the whole app; quick mode runs a 30-second smoke test; regression mode diffs results against a saved baseline. - Structured output: Generates a health score from a weighted rubric (console errors, broken links, visual, functional, UX), a Top 3 Things to Fix list, and a baseline.json for future regression runs. - Use Case: After merging a branch that changes the checkout flow, run the skill to automatically detect the local dev server, test the affected pages end-to-end, and receive a report with screenshots and repro steps for each bug found. ## Quick Start Ask the assistant to run a report-only QA pass on your local app at http://localhost:3000 and save the report to .gstack/qa-reports.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I test my web app without writing test code?

Run the skill with a target URL or on a feature branch. It navigates pages, clicks interactive elements, fills forms, checks console errors, and writes a structured report with screenshots and reproduction steps for each issue found.

What is diff-aware QA testing on a feature branch?

Diff-aware mode analyzes the git diff between your branch and main, maps changed files to affected pages and routes, then tests only those pages in a browser. It cross-references commit messages to verify the change does what it intended.

Does this QA skill fix the bugs it finds?

No. It is strictly report-only: it documents issues with screenshot evidence, severity, and repro steps, but never modifies code. For a test-fix-verify loop, use the full /qa skill instead.

Can I run regression testing against a previous QA report?

Yes. Pass a baseline.json from a prior run with the regression flag. The skill compares health scores, lists fixed issues, lists new issues, and appends a regression section to the new report.

How does the skill handle login and authentication during testing?

It supports signing in with provided credentials through the login form or importing cookies from a JSON file. For 2FA it asks the user for the code, and for CAPTCHAs it pauses until the user completes the challenge.

What are the limitations of automated browser QA?

It cannot complete CAPTCHAs or 2FA without user help, may miss issues requiring domain knowledge, and SPA navigation detection depends on snapshot inspection rather than link crawling. It also requires a reachable running app.