shipping-and-launch

Prepares .NET production launches with pre-launch checklists, feature flags, staged rollouts, and rollback plans.

7|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/peterblazejewicz/claude-plugins --skill shipping-and-launch-peterblazejewicz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-and-launch
Source: https://github.com/peterblazejewicz/claude-plugins/tree/main/plugins/dotnet-skills/skills/shipping-and-launch
Command: npx skills add https://github.com/peterblazejewicz/claude-plugins --skill shipping-and-launch-peterblazejewicz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying .NET applications to production without a structured process leads to missed security checks, unmonitored releases, and no tested rollback path when something breaks. This Skill provides a complete launch framework so every deployment is reversible, observable, and incremental. ## Core Features & Use Cases - Pre-Launch Checklist: Covers code quality (dotnet test, dotnet build -warnaserror), security (dotnet list package --vulnerable, authorization, CORS), performance (EF Core N+1 detection, caching, BenchmarkDotNet), accessibility, infrastructure, and documentation. - Feature Flags & Staged Rollout: Implements flags via IOptions<T> or Microsoft.FeatureManagement, with a 6-stage rollout sequence (staging → production → team → 5% canary → gradual → full) and green/yellow/red decision thresholds for error rates, latency, and GC metrics. - Monitoring & Rollback: Wires up OpenTelemetry, Application Insights, and ILogger scopes, plus a documented rollback plan including EF Core migration rollback via dotnet ef database update and expand-contract schema changes. - Use Case: Before releasing a new ASP.NET Core feature backed by an EF Core migration, run through the checklist, deploy behind a feature flag, canary to 5% of users while watching Application Insights, and keep a tested migration rollback path ready. ## Quick Start Ask the assistant to prepare a production launch plan for your .NET feature, including the pre-launch checklist, feature flag setup, staged rollout thresholds, and an EF Core migration rollback strategy.

Frequently Asked Questions about shipping-and-launch

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

FAQPage Schema
How do I prepare a .NET application for production deployment?

Run the pre-launch checklist: verify dotnet test and dotnet build -warnaserror pass, check dotnet list package --vulnerable for Critical or High vulnerabilities, confirm authorization and security headers, and ensure health check endpoints and structured logging are configured before deploying.

How to implement feature flags in ASP.NET Core?

Bind flags with IOptions<FeatureOptions> from configuration using ValidateDataAnnotations and ValidateOnStart, or use Microsoft.FeatureManagement with IFeatureManager for runtime toggling. Azure App Configuration feature filters support percentile-based gradual rollouts.

How do I roll back an EF Core migration in production?

Run dotnet ef database update with the previous migration name, specifying the project and startup project. For destructive changes, prefer the expand-contract pattern: add new schema first with dual-writes, then drop old columns in a later release.

What metrics should I monitor during a canary rollout?

Track HTTP 5xx and exceptions per minute, p95 latency, Gen2 GC collections, thread-pool queue length, and business metrics. Roll back if errors exceed 2x baseline or p95 latency rises more than 50 percent above baseline.

When should I not use a big-bang release strategy?

Avoid big-bang releases for any deployment carrying risk, which is effectively all of them. Staged rollouts behind feature flags let you canary to 5 percent of users, monitor for 24-48 hours, and roll back by flipping a flag instead of redeploying.