qa

Tests web applications, fixes found bugs in source code, and re-verifies with atomic commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually testing a web app before shipping is slow and easy to skip, and bugs found late cost more to fix. This Skill acts as a QA engineer and bug-fix engineer in one: it clicks through your app like a real user, finds bugs, fixes them in source code with atomic commits, and re-verifies each fix. ## Core Features & Use Cases - Test-Fix-Verify Loop: Systematically explores pages, forms, and states, then fixes critical/high/medium/low issues depending on the chosen tier (Quick, Standard, Exhaustive). - Structured QA Reports: Produces before/after health scores, severity-classified issues with screenshot evidence, regression tests, and a ship-readiness summary. - Diff-Aware and Regression Modes: Automatically scopes testing to your feature branch changes, or compares against a saved baseline to catch regressions. - Use Case: You just finished a billing page on a feature branch and ask "does this work?" The Skill tests the changed pages, finds a broken form validation, commits the fix, and reports the health score improvement. ## Quick Start Ask the AI to run /qa on your local dev server URL to test the app, fix any bugs it finds, and show a ship-readiness report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test my web app and fix bugs before shipping?▼

Run the qa skill against your app's URL or let it auto-detect your feature branch changes. It explores pages like a real user, classifies issues by severity, fixes them in source code with atomic commits, and re-verifies each fix with before/after evidence.

What testing tiers does the QA workflow support?▼

Three tiers control which issues get fixed: Quick covers critical and high severity only, Standard adds medium severity, and Exhaustive includes low and cosmetic issues. Standard is the default tier.

Can I run QA only on the changes in my feature branch?▼

Yes. If no URL is given and you are on a feature branch, the skill enters diff-aware mode automatically, scoping tests to pages affected by your branch changes. You can also pass a scope like a specific page.

Does the QA skill support regression testing against previous runs?▼

Yes. Pass a baseline report file with the regression flag to compare current results against a previous run. The report shows health score deltas, issues fixed since baseline, and new issues introduced.

Why does the QA skill require a clean git working tree?▼

Each bug fix gets its own atomic commit, so uncommitted changes would mix with fix commits. If the tree is dirty, the skill asks you to commit or stash your changes before starting.

What happens if my project has no test framework set up?▼

The skill detects your runtime, researches current best practices, and offers to bootstrap a framework like vitest, pytest, or minitest with example tests, CI configuration, and a TESTING.md guide. You can decline and it will skip bootstrap.