testing-qa

Create structured test plans for unit, integration, and E2E testing scenarios.

Updated May 6, 2026
One-click install
npx skills add https://github.com/korwlik23/skills --skill testing-qa-korwlik23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-qa
Source: https://github.com/korwlik23/skills/tree/main/v1/testing-qa
Command: npx skills add https://github.com/korwlik23/skills --skill testing-qa-korwlik23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you prevent regressions and avoid shipping fragile code by guiding thorough test coverage, debugging flaky behavior, and preparing production-ready QA plans.

Core Features & Use Cases

It structures unit, feature/integration, and E2E testing into practical checklists, provides quality rules for deterministic and independent tests, and includes a production release QA test plan template for gauging confidence. It is useful when you are adding or reviewing tests, investigating a failing or flaky CI pipeline, improving test infrastructure, or validating readiness for a release.

Quick Start

Use the testing-qa skill to create a prioritized Test Plan and CI-ready test checklist for the requested change without inventing coverage results or pretending tests were run.

Frequently Asked Questions about testing-qa

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

FAQPage Schema
How do I create a QA checklist for production release readiness?

Fix flaky tests by enforcing deterministic and independent test execution within your CI pipeline. This skill provides quality rules and debugging guidance to isolate flaky behavior, address regressions, and structure test infrastructure for reliable, reproducible CI runs.

What is the best way to structure E2E testing and regression testing coverage?

Designing CI pipeline stages for test automation requires integrating deterministic, isolated, and readable test guidance into your build process. This skill helps structure unit, feature/integration, and E2E testing scenarios into CI-ready checklists to prevent regressions and avoid shipping fragile code.

Does this testing and QA plan approach work for unit and feature integration testing?

Yes, this approach applies to unit, feature/integration, and E2E testing scenarios. It structures these test types into practical checklists with quality rules for deterministic and independent tests, providing explicit evidence of what was run and what was not for operational use.

Why does my test coverage plan lack evidence of what was actually run?

Test coverage plans lack evidence when they do not output structured test plans with explicit operational details. This skill ensures deterministic, isolated, readable test guidance and provides a structured Test Plan documenting exactly what was run and what was not, without inventing coverage results.