qa

Identify, reproduce, and fix web application defects with atomic commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a repeatable QA workflow to systematically test a web application, reproduce defects, and verify fixes through atomic commits and re-verification.

Core Features & Use Cases

  • Structured QA passes with Quick/Standard/Exhaustive tiers for different risk levels.
  • Atomic fixes with per-fix commits and re-verification to ensure traceability.
  • Proactive guidance when asked questions like 'does this work?' and feature readiness signals.

Quick Start

Run the QA cycle at your target tier and review before/after evidence to verify fixes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically reproduce and fix web application bugs?

To systematically reproduce and fix web application bugs, apply a structured QA workflow that identifies defects, applies atomic code fixes with per-fix commits, and re-verifies changes to ensure traceability. This process yields before/after health scores and a ship-readiness summary.

What is the difference between quick, standard, and exhaustive QA campaigns?

Quick, standard, and exhaustive QA campaigns are structured testing tiers designed for different risk levels. They scale the depth of bug identification and verification, allowing you to match the rigor of deterministic task execution to the specific risk profile of your web application changes.

How to verify code fixes with atomic commits during bug-fix verification?

Verify code fixes during bug-fix verification by applying atomic fixes that generate per-fix commits and re-verify the changes. This deterministic execution approach provides fix evidence and before/after health scores to confirm the web application defect is resolved.

Does this QA workflow provide evidence for ship-readiness?

Yes, this QA workflow provides evidence for ship-readiness by generating before/after health scores, fix evidence, and a final ship-readiness summary. It proactively guides feature readiness when evaluating if a web application works correctly.

When should I use an exhaustive QA pass instead of a quick test?

Use an exhaustive QA pass instead of a quick test when your web application changes carry higher risk levels. The exhaustive tier performs deeper defect identification and re-verification to ensure fewer bugs reach production compared to a quick pass.