skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

quality-gates

Validate and enforce quality gates across CI/CD workflows with pass/fail reports.

35|8|Updated Feb 6, 2026
Search Tags:#reporting#governance#traceability#ci-cd#quality-gates#gate-validation
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill quality-gates-microsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-gates
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/quality-gates
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill quality-gates-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quality gate validation ensures every workflow stage meets standards before progression, reducing defects and ensuring compliance.

Core Features & Use Cases

  • Supports four gate types: spec-quality, spec-to-plan, plan-to-tasks, completeness, with pass/fail reporting.
  • Generates actionable feedback and traceability to guide remediation.
  • Ideal for CI/CD governance, compliance checks, and release readiness verification.

Quick Start

Invoke the quality gate for the active workflow by setting type to spec-quality to produce the checklists and reports.

Frequently Asked Questions about quality-gates

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

FAQPage Schema
How do I enforce quality gates across CI/CD workflows to prevent progression?▼

To enforce quality gates across CI/CD workflows, you must validate each stage using a mandatory type parameter. This ensures gates pass before progression by producing pass/fail reports and actionable feedback for compliance.

What types of quality gate validation can I perform for release readiness?▼

Quality gate validation supports four types: spec-quality, spec-to-plan, plan-to-tasks, and completeness. These gate types ensure workflow stages meet standards by generating pass/fail reports and traceability for release readiness.

How do I generate actionable feedback for failed CI/CD compliance checks?▼

Generating actionable feedback for failed compliance checks involves running gate validation on your active workflow. The process outputs pass/fail reports with specific traceability details to guide remediation and ensure compliance.

Can I use this quality gate validation for code review tasks?▼

Quality gate validation explicitly excludes code review or implementation tasks. It is designed strictly for workflow governance, applying only to spec-quality, spec-to-plan, plan-to-tasks, and completeness gate checks.

Do I need to configure a mandatory parameter to validate spec quality?▼

Yes, validating spec quality requires configuring a mandatory type parameter set to spec-quality. Invoking this gate type on the active workflow produces the necessary checklists and pass/fail reports for progression.

When do I need completeness gates in my CI/CD governance process?▼

Completeness gates are needed in CI/CD governance when verifying release readiness before progression. They validate that all workflow stages meet defined standards, producing pass/fail reports and actionable traceability to reduce defects.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

using-git-worktrees

Create an isolated Git worktree for feature development without disrupting the current workspace.

Community
Intermediate
BasharAmsoBasharAmso
1

Launch Checklist

Automate pre-launch validation and generate a pass/fail readiness report.

Community
Intermediate
Avila-TekAvila-Tek

ci-cd-and-automation

Automate CI/CD quality gates with lint, type-check, tests, and builds.

Official
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate