dotnet-devops-release-safety

Enforce CI build, test, deployment, and rollback gates for .NET releases.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/MartiXDev/ai-dev-strategy --skill dotnet-devops-release-safety-martixdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-devops-release-safety
Source: https://github.com/MartiXDev/ai-dev-strategy/tree/main/plugins/dotnet-devops-release/skills/dotnet-devops-release-safety
Command: npx skills add https://github.com/MartiXDev/ai-dev-strategy --skill dotnet-devops-release-safety-martixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping .NET applications to production without structured release gates leads to broken deployments, untested rollouts, and rollbacks that fail under pressure. This Skill provides a disciplined gate-by-gate checklist that hardens CI/CD pipelines before production exposure. ## Core Features & Use Cases - Build and Test Gates: Enforce Release-configuration builds, warning-as-error policies, immutable versioned artifacts, and green unit/integration suites with flaky-test blocking. - Deployment Preflight and Controlled Rollout: Validate environment configuration, secrets, feature flags, and database migration safety, then require progressive rollout (canary, ring, or blue-green) with measurable promotion criteria and approval checkpoints. - Rollback Readiness and Post-Deploy Verification: Keep last-known-good artifacts deployable, define rollback triggers and runbooks, and capture release evidence against SLO/SLA health. - Use Case: Before promoting a .NET API release to production, walk through all six gates to confirm artifacts are versioned, smoke tests pass, the migration strategy is documented, and the rollback plan is executable without extra preparation. ## Quick Start Ask the AI to review your .NET release pipeline against the six release safety gates and list any missing checks before go-live.

Frequently Asked Questions about dotnet-devops-release-safety

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

FAQPage Schema
How do I add release safety gates to a .NET CI/CD pipeline?

Add sequential gates covering build integrity, test quality, deployment preflight, controlled rollout, rollback readiness, and post-deploy verification. Each gate must pass with traceable evidence before the release proceeds to the next stage.

What should a .NET deployment preflight check include?

A deployment preflight check should validate environment-specific configuration, secrets references, and feature-flag defaults. It should also confirm the database migration strategy is safe and verify readiness and liveness probe endpoints plus dependency connectivity.

How do I make a .NET release rollback-ready?

Keep the last-known-good artifact immediately deployable and define clear rollback trigger thresholds with assigned ownership. Validate the rollback runbook steps, communication channel, and execution command before go-live so no extra preparation is needed.

Why use canary or blue-green deployment instead of all-at-once release?

Progressive rollout limits blast radius by exposing only a subset of traffic to the new version first. It lets you measure promotion criteria such as error rate, latency, and saturation before full cutover, with explicit approval checkpoints between stages.

When should a release be blocked by test results?

Block the release when unit or integration suites are not green, critical smoke tests fail, flaky tests remain unresolved, or critical suites are skipped. Non-regression guardrails like coverage trends or static analysis severity should also hold.