qa

Detect defects and regressions in web applications across three testing tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify and reproduce defects in web applications, reducing release risk and surfacing regressions early.

Core Features & Use Cases

  • Structured testing across feature states to uncover critical, high, medium, and cosmetic issues.
  • Bug documentation and evidence with before/after health scores, logs, and screenshots to enable fast fixes.
  • Ship-readiness assessment that summarizes test results and readiness for deployment across three tiers: Quick, Standard, Exhaustive.

Quick Start

Run the QA workflow on a newly implemented feature to detect, document, and verify defects before shipping.

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 a release?

Web application bug testing before release requires structured testing across feature states to uncover critical, high, medium, and cosmetic issues. This process systematically identifies and reproduces defects to reduce release risk and surface regressions early.

What is the best way to document bug evidence for fast triage and fixes?

Bug documentation for fast fixes requires capturing before and after health scores, logs, and screenshots. This evidence enables fast triage and bug triangulation while enforcing atomic commits for applied fixes.

How do I verify ship-readiness and perform deployment verification?

Ship-readiness verification summarizes test results and deployment readiness across Quick, Standard, and Exhaustive testing tiers. It performs release verification to confirm whether the application is ready for deployment.

How do I write regression tests after fixing a bug in a web application?

Writing regression tests after bug fixes is enforced by the workflow during re-verification. It ensures atomic commits for applied fixes and performs re-verification to detect regressions in web applications.

Does this QA testing workflow support different levels of test coverage?

This QA testing workflow supports different levels of test coverage through Quick, Standard, and Exhaustive tiers. These tiers scale the testing depth applied during feature testing, bug triangulation, and deployment verification.