qa-only

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

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill qa-only-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/no-session/pstack/tree/main/qa-only
Command: npx skills add https://github.com/no-session/pstack --skill qa-only-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Solo founders and developers need to know what is broken in their web app without mixing testing and fixing into one step. This Skill systematically tests a web application like a real user and delivers a structured QA report with a health score, screenshots, and repro steps, while never touching the source code. ## Core Features & Use Cases - Report-only browser testing: Clicks through pages, fills forms, checks console errors, and documents issues with screenshot evidence, but never edits files 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 billing page change on a feature branch. Run the Skill with no arguments and it auto-detects your local dev server, tests the affected routes, and writes a report with screenshots and repro steps to .pstack/qa-reports/. ## Quick Start Ask the AI to run a report-only QA pass on your local app at http://localhost:3000 and save the findings to the qa-reports directory.

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 app's URL. It systematically clicks through pages, fills forms, and checks console errors, then writes a structured report with screenshots and repro steps. It never edits source code or suggests fixes.

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

qa-only is report-only: it finds and documents bugs but never fixes anything. The full /qa skill runs a test-fix-verify loop where issues are corrected and retested. Use qa-only when you want a bug report without code changes.

Can I QA test changes on a feature branch before merging?

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

How does regression testing work with a saved baseline?

Pass --regression with a baseline.json from a previous run. The skill runs a full test, then diffs results: which issues were fixed, which are new, and how the health score changed. A regression section is appended to the report.

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

The skill drives a real browser through a compiled browse binary that must be built once, taking about 10 seconds. If the binary is missing, the skill asks permission, runs the setup script, and installs bun if needed.