qa

Run QA tests on web applications, apply fixes, and re-verify results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing identifies bugs and ensures fixes are verified across deploys, reducing regression risk and manual toil.

Core Features & Use Cases

  • Automated QA testing across web apps
  • Atomic commits for each fix and re-verification
  • Proactive bug-fix iteration with ship-readiness summaries and health scores

Quick Start

Run the QA workflow on the target URL with a chosen tier and scope to start testing.

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 QA testing and bug fixing in a single workflow?

The QA workflow requires a clean repository state before testing begins. You run it on a target URL with a chosen tier and scope to start testing, and it supports atomic commits for each applied fix.

Can I use this QA workflow for exhaustive regression checks across features?

The workflow outputs health scores, evidence, and ship-readiness summaries. It also integrates planning templates, reports, and optional telemetry to track release quality.

Do I need a clean repository state to run automated QA tests?

A clean repository state is required to run automated QA tests and apply bug fixes. This ensures atomic commits for each fix are tracked properly without conflicting changes.

What's the best way to verify bug fixes and reduce regression risk in web apps?

The best way to verify bug fixes and reduce regression risk is an automated QA workflow that runs tests, applies atomic commits for each fix, and re-verifies results with health scores and evidence.