qa

Run automated and interactive QA sessions to test, fix, and re-verify web applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically test web applications, find functional and UI bugs, apply atomic fixes in source, and re-verify so teams ship with evidence and confidence.

Core Features & Use Cases

  • Iterative Test-and-Fix Workflow: Runs interactive/browser-backed QA sessions, records console/errors/screenshots, and commits atomic fixes for each issue found.
  • Tiered Coverage & Modes: Quick, Standard, and Exhaustive tiers control severity coverage; diff-aware mode targets feature branches; CDP integration uses the user's real browser session when available.
  • Bootstrap & Reporting: Detects or bootstraps test frameworks, creates CI/test artifacts, and emits structured QA reports with before/after health scores, issues, and regression data.

Quick Start

Run the qa skill on your current branch or provide a target URL to test, fix, and verify the web app in iterative atomic commits.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web app testing and bug fixing on a feature branch?

Automated QA sessions run on feature branches to discover, fix, and re-verify functional and UI bugs. The workflow requires a clean git working tree and commits atomic fixes for each issue found, producing structured reports and screenshots.

Can I run regression testing against a live URL using my real browser session?

Regression testing can target live URLs or local development servers using an optional browser CDP connection. This integration leverages your real browser session to interactively test, record console errors, and capture screenshots during the QA workflow.

What is diff-aware mode for automated web testing?

Diff-aware mode is a targeted testing approach that focuses QA sessions specifically on feature branches. By analyzing changes, it efficiently discovers and fixes newly introduced defects rather than testing the entire web application repeatedly.

Do I need a pre-existing test framework to run automated QA sessions?

You do not need a pre-existing test framework. The QA process detects or bootstraps the necessary test frameworks automatically, creates CI/test artifacts, and generates structured QA reports with before and after health scores.

What is the best way to systematically find and fix UI bugs in web applications?

Systematically finding and fixing UI bugs involves running tiered QA sessions that record errors and capture screenshots. The process applies atomic source fixes and re-verifies defects, providing before and after health scores to ensure teams ship with evidence.

What are the limitations of running automated QA and bug fixing workflows?

A primary limitation is the strict requirement for a clean git working tree before initiating any QA session. Additionally, utilizing a real browser session for interactive testing depends on successfully establishing an optional browser CDP connection.