qa

Automate end-to-end QA testing and atomic bug fixes for web applications.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill qa-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/qa
Command: npx skills add https://github.com/timurgaleev/vibestack --skill qa-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying.

Core Features & Use Cases

  • Structured QA workflow: test, log evidence, and escalate issues.
  • Atomic fixes: each bug fix is committed independently and re-verified.
  • Evidence-rich reports: generate comprehensive QA reports with before/after evidence and health metrics.

Quick Start

Invoke /qa to start a baseline QA pass and generate a structured report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end QA testing and fix bugs in a web application?

To automate QA testing and fix bugs, run a guided QA workflow that logs defects, applies code fixes in small independent commits, and re-verifies the results to ensure the web application functions correctly.

How are bug fixes committed during the automated QA workflow?

Bug fixes are committed atomically during the automated QA workflow, meaning each fix is committed independently and then re-verified to isolate changes and maintain clean version-controlled code history.

What do I need to run automated QA testing workflows on my project?

To run automated QA testing workflows, you need a local vibestack environment and version-controlled code to perform tests, commit atomic fixes, and re-verify outcomes.

How do I generate evidence-rich QA reports for my web app?

You can generate evidence-rich QA reports by running a baseline QA pass that produces comprehensive reports containing before and after evidence alongside application health metrics.

Can I use this automated QA workflow across different projects?

Yes, the automated QA workflow applies across projects by running guided testing, logging defects, fixing code atomically, and re-verifying outcomes regardless of the specific web application.

What is the best way to handle defect logging and source code fixes?

The best way to handle defect logging and source code fixes is to run a structured QA workflow that logs evidence, escalates issues, fixes code in small commits, and re-verifies the results.