qa-release-gate-triage

Classifies defects by severity and impact to determine go/no-go release readiness.

3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/junchenghuo/openclaw-biz-agent --skill qa-release-gate-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-release-gate-triage
Source: https://github.com/junchenghuo/openclaw-biz-agent/tree/main/qa/.agents/skills/qa-release-gate-triage
Command: npx skills add https://github.com/junchenghuo/openclaw-biz-agent --skill qa-release-gate-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the QA release gate process by providing a structured approach to defect triage, release decision-making, and risk assessment.

Core Features & Use Cases

  • Defect Classification: Categorizes defects based on severity and impact.
  • Release Decision Support: Provides clear criteria for release go/no-go decisions.
  • Risk Assessment: Identifies and articulates potential testing risks.
  • Use Case: Before a major software release, the QA team uses this skill to systematically review all open bugs, decide which ones must be fixed before release, and document any accepted risks for the product owner.

Quick Start

Use the qa-release-gate-triage skill to classify defects and determine release readiness for the current build.

Frequently Asked Questions about qa-release-gate-triage

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

FAQPage Schema
How do I automate QA release gate triage for software deployments?

QA release gate triage is automated by classifying defects based on severity and impact, establishing release criteria, and providing structured risk assessment for go/no-go deployment recommendations. It systematically reviews open bugs to determine release readiness for the current build.

What is the best way to classify defects by severity and impact before a release?

Defect classification by severity and impact involves categorizing open bugs to systematically review which ones must be fixed before release. This structured approach supports go/no-go release decisions and documents accepted risks for the product owner.

How does risk assessment work for go/no-go release decisions?

Risk assessment for go/no-go release decisions works by identifying and articulating potential testing risks against established release criteria. It provides structured decision-making support to determine software deployment readiness and outlines necessary re-testing plans.

Can I use this defect triage process for a major software release?

Yes, you can use this defect triage process for a major software release. The QA team uses it to systematically review all open bugs, decide which defects must be fixed before release, and document any accepted risks for the product owner.

What criteria are used for release readiness decisions in quality assurance?

Release readiness criteria in quality assurance are established by evaluating classified defects based on their severity and impact. This structured decision-making process provides clear go/no-go recommendations and outlines necessary re-testing plans for software deployments.