qa-only

Tests web applications in a browser and produces structured bug reports with screenshots and health scores.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill qa-only-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack-qa-only
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill qa-only-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually clicking through a web app to find bugs is slow and inconsistent, and developers often ship branch changes without verifying they actually work in the browser. This Skill acts as a QA engineer that systematically tests a web application like a real user and produces an evidence-backed report — without ever touching the source code. ## Core Features & Use Cases - Report-only testing: Explores pages, clicks interactive elements, fills forms, checks console errors, and documents issues with screenshot evidence and repro steps — but never fixes anything. - Multiple modes: Diff-aware mode automatically scopes testing to files changed on a feature branch; Full mode systematically explores every reachable page; Quick mode runs a 30-second smoke test; Regression mode diffs results against a saved baseline. - Structured output: Generates a report with a weighted health score (console, links, visual, functional, UX, performance, content, accessibility), severity-ranked issues, a Top 3 Things to Fix list, and a baseline.json for future regression comparisons. - Use Case: You just pushed a feature branch and want to verify it works before merging. Run the Skill with no arguments — it detects the branch diff, finds your local dev server, tests the affected pages in a real browser, and hands you a report with screenshots of anything broken. ## Quick Start Ask the AI to run a report-only QA pass on your app at http://localhost:3000 and save the results 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 for bugs without writing test code?

Invoke the Skill with a target URL or run it on a feature branch with no arguments. It opens a real browser, clicks through pages, fills forms, checks console errors, and writes a report with screenshots and repro steps for each issue found.

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

qa-only is report-only: it finds and documents bugs but never edits source code or suggests fixes. The /qa skill runs the full test-fix-verify loop, applying fixes and re-testing. Use qa-only when you want a bug report without any code changes.

Can QA testing be scoped to only the files changed on my branch?

Yes. When invoked on a feature branch without a URL, diff-aware mode analyzes the git diff, maps changed files to affected pages and routes, detects the running local app, and tests only what the branch touched.

Does browser-based QA work with React, Next.js, or other SPAs?

Yes. For single-page apps it uses interactive snapshots instead of link crawling to find client-side navigation, checks for hydration errors in Next.js, verifies history handling, and monitors console output after each interaction.

How does regression testing against a previous QA run work?

Each run saves a baseline.json with the health score and issue list. Running with --regression loads that baseline, then reports which issues were fixed, which are new, and the health score delta between runs.

What are the limitations of report-only QA testing?

It never reads source code or applies fixes, so it cannot verify root causes. It also requires a reachable running app and a one-time build of the browse binary; CAPTCHAs and 2FA require manual user intervention.