skills.rest
PiercingXX
PiercingXXCOMMUNITY
Explore all skills by this author →
GitHub

test-qa

Test critical user journeys and produce a ship/no-ship QA decision.

1|Updated Jul 9, 2026
Search Tags:#manual testing#regression testing#defect triage#severity classification#release qa#staging verification#ship no-ship
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill test-qa-piercingxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-qa
Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/test-qa
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill test-qa-piercingxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or risky releases by guiding QA through systematic, user-journey verification and severity-based defect triage.

Core Features & Use Cases

  • Manual user-journey testing: Validate critical flows in a real staging environment, including edge cases and error states.
  • Defect capture and severity triage: Classify issues into S0–S3, document reproducible steps, and drive fixes or routing decisions.
  • Regression-focused handoff: Ensure fixes are re-verified and that regression tests are added so the same failure cannot return.

Quick Start

Ask the AI to create a QA test matrix for the critical staging user journeys, run the required manual checks, and produce a ship/no-ship QA report with defect severity and regression test recommendations.

Frequently Asked Questions about test-qa

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

FAQPage Schema
How do I decide whether to ship a release after manual staging verification?▼

Release readiness is determined by validating critical user journeys in staging, triaging defects by severity S0–S3, and producing a final ship/no-ship decision based on the remaining risk profile.

What is the best way to triage defects using severity classification during regression testing?▼

Defect triage requires classifying issues into severity levels S0 through S3, documenting reproducible steps for each bug, and routing fixes based on their impact on critical user journeys before release.

How do I create a QA test matrix for critical user journeys and edge cases?▼

A QA test matrix maps critical staging user journeys to manual checks, including happy paths, error states, and edge cases like slow networks and expired auth, ensuring systematic release verification.

Does manual release QA require adding regression tests after verifying fixes?▼

Manual release QA requires re-testing fixes to verify defects are resolved and adding regression tests to the matrix, ensuring the same failure cannot return in future release cycles.

Can I use this for staging verification of error states and slow network edge cases?▼

Staging verification covers manual testing of error states and edge cases like slow networks and expired auth, validating that critical user journeys remain stable under adverse conditions.

Why do I need severity classification S0–S3 for a ship/no-ship decision?▼

Severity classification S0–S3 quantifies defect impact, allowing QA to prioritize critical fixes and objectively justify the ship/no-ship decision rather than relying on subjective release readiness.

Related Skills

Explore More Software Engineering Skills→
mahg-esmahg-es
3

test-case

Generate traceable test cases from requirements and user stories.

Official
Advanced
forbotsakeforbotsake
5

qa

Run automated QA cycles with tiered testing and ship-readiness reporting.

Official
Advanced
fgarofalo56fgarofalo56
6

azure-devops-pipelines

Build and manage Azure DevOps YAML pipelines for CI/CD workflows.

Community
Advanced
apexradiusapexradius

test-gen

Generate unit and integration tests for Vitest, Jest, and Playwright frameworks.

Official
Intermediate