qa

Run tiered QA tests on web applications and generate ship-readiness reports.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill qa-yahav123147
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/yahav123147/paid-ads-cro-skills/tree/main/skills/qa
Command: npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill qa-yahav123147

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you find bugs, verify fixes, and decide whether a web application is actually ready to ship.

Core Features & Use Cases

  • Tiered QA testing: Runs Quick, Standard, or Exhaustive testing depending on how deep you want to go, focusing on critical issues first.
  • Evidence-driven reporting: Produces before/after health scores, captured fix evidence, and a clear ship-readiness summary.
  • Iterative fix and re-verify: Fixes the problems it finds one atomic change at a time, then re-tests to avoid “fixed but broken again” regressions.
  • Report-only mode: Supports running QA without modifying code so you can review findings first, using /qa-only.

Quick Start

Use the qa skill to test the site and fix any bugs found on the current branch by running "/qa Standard".

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically test a web application for bugs before release?

Systematically test a web application for bugs before release by running tiered QA testing that identifies defects and applies iterative code fixes while re-verifying results for shipping confidence. You can choose Quick, Standard, or Exhaustive coverage depending on your required depth.

Can I run QA testing on my site without modifying any code?

You can run QA testing on your site without modifying any code by using the report-only mode. This executes the standard testing workflow, generates before and after health scores, and produces a ship-readiness summary without applying any fixes to your branch.

What is the best way to verify bug fixes and prevent regressions in web apps?

The best way to verify bug fixes and prevent regressions in web apps is to apply iterative, atomic code changes and then re-test the application. This fix and re-verify cycle ensures that resolved bugs do not reappear and provides evidence-driven shipping confidence.

Does this QA process generate evidence and health scores for ship readiness checks?

Yes, this QA process generates evidence and health scores for ship readiness checks. It produces before and after health scoring, captures evidence of applied fixes, and outputs a clear summary to help you decide whether your web application is actually ready to ship.

How do I diagnose broken workflows during feature-readiness checks?

Diagnose broken workflows during feature-readiness checks by executing systematic QA testing that identifies defects across your web application. The process focuses on critical issues first and applies iterative fixes, verifying that the broken workflows are fully resolved before release.

What are the limitations of using automated regression verification for web application testing?

Automated regression verification for web application testing is limited to identifying defects, diagnosing broken workflows, and applying iterative fixes on your current branch. It focuses on tiered coverage and ship readiness rather than comprehensive exploratory or load testing outside its defined scopes.