qa

Test web applications, fix bugs, and generate health scores with tiered QA.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, repeatable QA process to identify defects, verify fixes, and deliver a ship-ready report for web applications.

Core Features & Use Cases

  • Structured QA workflow: plan, test, fix, and verify with before/after evidence.
  • Tiered testing: Quick, Standard, Exhaustive to match risk and urgency.
  • Evidence-driven reporting: generate health scores and a ship-readiness summary to guide deployment decisions.
  • Use case: A developer on a feature branch runs QA to validate fixes before merging.

Quick Start

Run QA on your target URL to test for critical issues, fix them atomically, and re-verify.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing for a web application and fix bugs before merging?

Automated QA testing systematically evaluates your web application to identify defects, apply atomic bug fixes, and verify the results with before and after evidence. It delivers a ship-readiness summary to validate changes before deployment.

What is the best way to generate QA evidence and health scores for a web app?

QA evidence and health scores are generated through a structured testing workflow that evaluates your web application, documents defects, and produces verifiable metrics. These metrics guide deployment confidence and track application health.

How do I scope web application testing when I have limited time before a release?

You can scope web application testing using three tiers: Quick, Standard, and Exhaustive. These tiers align testing depth with your risk and urgency, delivering appropriate health scores and a ship-readiness summary for the release.

Can I use automated QA testing to verify bug fixes and produce a ship-readiness report?

Automated QA testing verifies bug fixes by re-testing the web application after changes are applied. It produces a ship-readiness report that includes health metrics and verifiable evidence to confirm stability before deployment.

Does this QA testing process work for a developer validating fixes on a feature branch?

Yes, this QA testing process is designed for developers on feature branches. It validates bug fixes locally, generates before and after health scores, and provides evidence to ensure the branch is ready for merging.

Why do I need atomic commits when fixing bugs found during web application testing?

Atomic commits isolate individual bug fixes applied during web application testing. This practice ensures fixes are verifiable and traceable, maintaining clean version control while generating evidence for a ship-readiness summary.