qa

Run tiered QA passes on web applications with bug replication and re-verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing systematically identifies bugs in a web application, guiding iterative fixes and validating stability before release.

Core Features & Use Cases

  • Tiered QA coverage: Quick, Standard, Exhaustive, with before/after health scores and ship-readiness summaries.
  • Iterative bug fixing: Reproduces bugs, commits fixes atomically, and re-verifies fixes in source code.
  • Proactive guidance: Suggests testing hardening when features are ready for review or questions arise about "does this work?".

Quick Start

Start a QA pass on the current build and verify fixes against the bug list.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run regression testing on a web application build?

Regression testing on a web application build is executed through tiered QA coverage, allowing you to perform standard regression passes that reproduce bugs and verify fixes against the source code.

What is the best way to systematically find and fix bugs before release?

Systematic bug finding before release is achieved through iterative QA testing that reproduces bugs, commits atomic fixes, and re-verifies stability while tracking before and after health scores.

Can I get a ship-readiness report after completing a QA pass?

Yes, a ship-readiness report is generated after a QA pass, summarizing tiered coverage levels and health scores to validate web application stability before release.

Does this QA testing process support quick checks or only exhaustive testing?

The QA testing process supports both quick checks and exhaustive testing through tiered coverage, scaling from fast validations to in-depth bug replication and iterative fixes.

How do I verify bug fixes in source code after a regression test?

Bug fixes in source code are verified by re-running the QA workflow, which atomically commits fixes and performs re-verification to ensure the web application bug is resolved.