qa

Automate QA testing and iterative bug fixing for web applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend too much time manually testing web applications and chasing flaky bugs. This Skill automates a repeatable QA workflow that executes tests, captures evidence, and coordinates atomic bug fixes.

Core Features & Use Cases

  • End-to-end QA cycles for web apps, including test execution, bug reproduction, and health scoring.
  • Iterative fixes with atomic commits and re-verification, delivering a ship-readiness summary.
  • Generates before/after health scores and evidence to guide releases.

Quick Start

Run a QA workflow against your web app by providing the target URL and optional tier, then review the health and evidence.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing for a web application?

Automate QA testing for a web application by running a workflow that executes tests, captures before and after evidence, and generates a ship-readiness summary. The process requires a test framework, Git for commits, and access to the target app to verify results.

What is a ship-readiness summary in automated QA workflows?

A ship-readiness summary in automated QA workflows is a final report generated after iterative bug fixes and re-verification. It uses before and after health scores and captured evidence to guide release decisions for web applications.

Do I need a test framework and Git to automate bug fixing?

Yes, you need a test framework and Git to automate iterative bug fixing. The workflow requires Git to make atomic commits for each fix and a test framework to execute tests and verify results against the target web app.

Can I generate health scores for frontend and backend web flows?

Yes, you can generate health scores for both frontend and backend web flows. The QA workflow applies across these flows, producing health scores and evidence to evaluate the stability of each fix or release.

What's the best way to coordinate atomic bug fixes during QA cycles?

Coordinate atomic bug fixes during QA cycles by automating the workflow to reproduce bugs, apply fixes, and make atomic Git commits. The system then re-verifies the web app and updates the health score to ensure stability.

Why does automated QA require access to the target app?

Automated QA requires access to the target app to run tests and verify results directly within the environment. This access allows the workflow to execute frontend and backend flows, capture evidence, and accurately reproduce bugs for iterative fixes.