qa-only

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

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill qa-only-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill qa-only-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually clicking through a web app to find bugs is slow and inconsistent, and teams often ship changes without verifying pages actually work. This Skill performs systematic browser-based QA testing and produces an evidence-backed report — without ever modifying your code. ## Core Features & Use Cases - Report-only testing: Explores pages, fills forms, clicks interactive elements, and documents issues with screenshots and repro steps, but never fixes anything. - Multiple modes: Diff-aware mode tests only pages affected by your feature branch, Quick mode runs a 30-second smoke test, and Regression mode diffs results against a saved baseline. - Health scoring: Computes a weighted 0-100 health score across console errors, links, visual, functional, UX, performance, content, and accessibility categories. - Use Case: You just shipped a new checkout flow on a feature branch. Run the Skill with no URL and it auto-detects your local dev server, tests the pages changed in your diff, and writes a report with screenshots and a health score to .gstack/qa-reports/. ## Quick Start Ask the agent to run a report-only QA pass on your local app at localhost:3000 and produce a structured 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 QA test my web app without fixing the bugs found?

Invoke the qa-only skill with a target URL or on a feature branch. It systematically explores pages, tests forms and interactions, and writes a structured report with screenshots and repro steps, but never modifies any code.

How do I test only the pages changed in my feature branch?

Run the skill on a feature branch without providing a URL. It enters diff-aware mode, analyzes the git diff to identify affected routes, detects your local dev server on common ports, and tests only those pages.

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

qa-only is report-only: it documents bugs with evidence but never fixes them. The full /qa skill runs a test-fix-verify loop that also repairs the issues it finds. Use qa-only when you want a bug report without code changes.

Does the QA report include a health score?

Yes. The report computes a weighted 0-100 health score across console errors, broken links, visual, functional, UX, performance, content, and accessibility categories, plus a Top 3 Things to Fix summary.

Can I compare QA results against a previous run?

Yes. Use regression mode with a baseline.json file from a prior run. The skill diffs the results, reporting which issues were fixed, which are new, and the health score delta.

What are the limitations of browser-based QA testing?

The skill tests as a user and never reads source code, so it cannot diagnose root causes. Flows blocked by CAPTCHA or 2FA require manual user intervention, and it intentionally never fixes the bugs it finds.