qa

Execute end-to-end QA tests, document defects, and verify fixes with regression checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers systematically test web applications end-to-end, identify defects, and ensure fixes are verified before release.

Core Features & Use Cases

  • End-to-end testing with iterative bug fixing, atomic commits, and re-verification across Quick, Standard, and Exhaustive tiers.
  • Rich evidence collection: screenshots, console logs, and regression baselines for traceability.
  • Structured reporting and health scoring to guide release readiness.

Quick Start

Test the current app, reproduce defects, commit fixes atomically, and verify with regression checks to ensure ship-readiness.

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 and bug fixing for web apps?

Automate end-to-end QA testing by executing targeted tests across your web app to identify defects, then apply iterative bug fixes with atomic commits and re-run verification to close the loop.

What is regression testing and how does it verify bug fixes?

Regression testing verifies bug fixes by re-running end-to-end checks after applying atomic commits, ensuring the original defect is resolved without introducing new issues.

How do I generate a QA report with ship-readiness metrics and health scores?

Generate a structured QA report with health scores by executing end-to-end tests, collecting evidence like console logs and screenshots, and documenting issues for release decision-making.

Can I run exhaustive regression tests across different testing tiers?

You can run regression tests across Quick, Standard, and Exhaustive tiers, executing end-to-end QA checks, collecting traceability evidence, and applying atomic bug fixes with automated re-verification.

What is the best way to collect evidence and console logs during web app testing?

The best way to collect evidence during web app testing is to execute end-to-end QA tests that automatically capture screenshots, console logs, and regression baselines for traceability.

Why should I use atomic commits when fixing bugs during regression testing?

Use atomic commits during bug fixes to isolate each iterative change, ensuring that if a regression check fails during re-verification, the specific defect introduction point remains traceable.