qa

Run end-to-end QA tests across tiers and report ship-readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often struggle to systematically validate a web application, capture evidence of defects, and coordinate fixes across code and tests. This Skill provides a repeatable workflow that guides QA testing, documents health metrics, and ties results back to ship-readiness.

Core Features & Use Cases

  • End-to-end QA testing orchestration across quick, standard, and exhaustive tiers.
  • Proactive reporting with before/after health scores, fix evidence, and ship-readiness summaries.
  • Guidance for iterative bug fixing with atomic commits and re-verification.

Quick Start

Run automated QA tests on your web app, then review the before/after health scores and fix evidence before re-verifying.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end QA testing for a web application?

Run automated QA tests across quick, standard, and exhaustive tiers to validate your web app end-to-end. The workflow identifies defects, captures test evidence, and generates before/after health scores to document ship-readiness.

What is the best way to document bug fixes and verify changes during web app testing?

Use an iterative QA workflow that proposes fixes, validates them with automated tests and manual checks, and enforces traceability through atomic commits, test evidence, and structured ship-readiness summaries.

Can I run a quick health check on my web app before shipping?

Yes, run the quick test tier to generate immediate before/after health scores and fix evidence. This validates basic ship-readiness for your web app without executing the exhaustive testing tier.

Does the QA testing process integrate with existing project routing configurations?

Yes, the QA testing workflow integrates with the project's CLAUDE.md routing when needed. This ensures test orchestration, fix verification, and ship-readiness reporting align with your existing project configurations.

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

Quick, standard, and exhaustive test tiers scale the depth of end-to-end QA validation for your web app. You select a tier based on required coverage, and the workflow produces corresponding health scores, test evidence, and ship-readiness summaries.