Verify release readiness by checking tests, acceptance criteria, and evidence completeness.
npx skills add https://github.com/MajesteitBart/delano --skill quality-skill
Please help me install this Agent Skill. Skill: quality-skill Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/quality-skill Command: npx skills add https://github.com/MajesteitBart/delano --skill quality-skill
This Skill verifies that work is actually ready to ship by checking tests, acceptance criteria, and evidence before closure or merge.
Use the quality-skill to verify the current change set, run the required checks, and produce a pass or fail gate decision with evidence.
High-intent search queries and answers about installing and using this skill.
Release readiness verification requires checking test execution, acceptance criteria, and evidence completeness to produce a defensible gate decision before merge. This ensures unresolved critical defects are zero and validation reruns are logged.
Risk-based verification selects the appropriate depth of testing based on low, medium, or high risk levels. It validates completed change sets by applying risk-based checks and defect reviews to confirm quality before closure.
Automating gate decisions involves verifying the current change set, running required checks, and producing a pass or fail decision with evidence. This requires test execution, validation reruns, and confirming unresolved critical defects are zero.
Validation reruns are needed when verifying release readiness for completed change sets that require risk-based validation and defect review. They confirm that all required tests pass and evidence logging is complete before merge or closure.
Risk-based verification chooses the right depth of testing based on low, medium, or high risk, but release readiness still requires test execution, validation reruns, and evidence logging to confirm unresolved critical defects are zero before merge.
Imad-OuteAutomate final risk-based quality gate verification for software releases.
bravekingzhangClassify release risk and verify evidence for operational readiness.
micfreDiagnose CI failures and verify development Slices against acceptance criteria.
chijunzhengReview code across languages for defects, standards, and technical debt.
