qa

Test web applications for defects and document fixes with health scores.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill qa-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/qa
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill qa-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA tests a web application for defects and guides atomic fixes that improve stability and release confidence.

Core Features & Use Cases

  • End-to-end QA workflow: automated testing, bug filing, and regression checks across CI/CD pipelines.
  • Tiered coverage: Quick (critical/high), Standard (+ medium), Exhaustive (+ cosmetic) tests with health impact assessment.
  • Evidence and ship-readiness: before/after health scores, fix evidence, and a ship-readiness summary to communicate readiness.

Quick Start

Run QA on your app by saying "qa" to start the evaluation, watch the health progress, and commit fixes as you go.

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 web application testing and guide bug fixes?

Automated end-to-end web application testing runs defect checks across your app and guides atomic fixes. It executes bug-fixing cycles across multiple tiers and documents changes to improve release stability.

What is tiered QA coverage and how does it assess application health?

Tiered QA coverage applies layered test depths—Quick for critical defects, Standard for medium issues, and Exhaustive for cosmetic bugs. It evaluates severity to generate before and after health scores for your application.

How do I generate ship-readiness evidence and regression checks for a release?

Ship-readiness evidence is generated by running regression checks and documenting bug fixes throughout the testing cycle. The process outputs a summary report communicating release confidence alongside before and after health scores.

Can I use tiered QA testing within an existing CI/CD pipeline?

Yes, tiered QA testing integrates into CI/CD pipelines to execute automated regression checks. It files bugs, assesses health impact, and produces fix evidence required for continuous deployment confidence.

When should I use exhaustive testing instead of a quick QA check?

Use exhaustive testing when preparing for major releases requiring cosmetic, medium, and critical defect verification. Apply quick QA checks for rapid validation of only critical and high-impact application regressions.

Why does my web application need fix evidence and health scores before shipping?

Fix evidence and health scores quantify stability improvements before shipping. They document the transition from pre-test defect states to post-fix readiness, providing measurable confidence for release approval.