qa-only

Tests web applications via browser automation and produces structured QA reports without fixing anything.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill qa-only-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill qa-only-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 that exploratory testing and delivers a structured bug report with screenshots, repro steps, and a health score, while deliberately never modifying any code. ## Core Features & Use Cases - Report-only QA testing: Systematically explores pages, clicks interactive elements, fills forms, checks console errors, and documents issues with screenshot evidence, but never applies fixes. - Diff-aware mode: When run on a feature branch without a URL, analyzes the git diff to identify affected pages and routes, then tests exactly what changed against a locally running app. - Multiple modes and scoring: Supports full, quick smoke-test, and regression modes (diffing against a saved baseline.json), plus a weighted health score across console, links, visual, functional, UX, performance, content, and accessibility categories. - Use Case: After merging a branch that touches the checkout flow, run the skill to automatically detect the local dev server, test the affected pages end-to-end, and receive a report listing 5-10 evidenced issues with severity ratings and a Top 3 Things to Fix summary. ## Quick Start Ask the AI to run a report-only QA pass on your web app, for example by saying: run /qa-only on http://localhost:3000 and give me a bug report without changing any code.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I test a web app and get a bug report without fixing code?▼

Run the qa-only skill with a target URL or on a feature branch. It explores pages, clicks elements, fills forms, checks console errors, and writes a structured report with screenshots and repro steps, but never edits any source files.

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 them. The full /qa skill runs the complete test-fix-verify loop, applying fixes and re-testing. Use qa-only when you explicitly want a bug report without code changes.

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

Yes. When invoked without a URL on a feature branch, diff-aware mode analyzes git diff output to identify affected pages and routes, detects the running local app on common dev ports, and tests only what the branch changed.

Does the QA report support regression comparison between runs?▼

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

How is the web app health score calculated in QA reports?▼

The score is a weighted average across eight categories: console errors (15%), links (10%), visual (10%), functional (20%), UX (15%), performance (10%), content (5%), and accessibility (15%). Each category starts at 100 and deducts points per finding by severity.

What happens if the QA test hits a login page, CAPTCHA, or 2FA?▼

The skill supports authentication via provided credentials or cookie file import. For 2FA it asks the user for the code, and for CAPTCHAs it pauses and asks the user to complete the challenge in the browser before continuing.