ci-cd-and-automation

Automates CI/CD pipelines for .NET projects with quality gates, deployments, and rollback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up and maintaining reliable build and deployment pipelines for .NET projects is error-prone: teams skip quality gates, hardcode secrets, ship without rollback plans, and let flaky tests or slow pipelines erode trust in CI. This Skill provides production-grade pipeline patterns so every change passes formatting, build, test, and vulnerability checks before merge. ## Core Features & Use Cases - Quality Gate Pipelines: GitHub Actions and Azure DevOps YAML enforcing dotnet format --verify-no-changes, dotnet build -warnaserror, dotnet test, and dotnet list package --vulnerable on every pull request. - Testing & Deployment Workflows: EF Core migrations with PostgreSQL services or Testcontainers, Playwright.NET E2E setup, NuGet package publishing, preview deployments per PR, feature flags via Microsoft.FeatureManagement, staged rollouts, and slot-swap rollback. - Use Case: You are bootstrapping a new ASP.NET Core service. Use this Skill to generate a complete CI workflow with format/build/test gates, an integration-test job against PostgreSQL, Dependabot grouping for Microsoft.* packages, and a manual rollback workflow using Azure App Service slot swaps. ## Quick Start Set up a GitHub Actions CI pipeline for my .NET 8 project with format checks, warnings-as-errors build, tests, and a vulnerability scan.

Frequently Asked Questions about ci-cd-and-automation

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

FAQPage Schema
How do I set up a CI pipeline for a .NET project with GitHub Actions?

Use actions/setup-dotnet@v4 with your global.json, then run dotnet restore, dotnet format --verify-no-changes, dotnet build -warnaserror, and dotnet test as sequential steps. Add dotnet list package --vulnerable for a security gate and upload test results with actions/upload-artifact.

How to run integration tests with PostgreSQL in GitHub Actions?

Define a postgres:16 service container with health checks, apply EF Core migrations via dotnet ef database update, then run dotnet test with the connection string passed through the ConnectionStrings__Default environment variable. Prefer Testcontainers inside the test project to keep CI YAML simple.

Does dotnet list package --vulnerable fail the build on vulnerabilities?

No, dotnet list package --vulnerable exits 0 even when vulnerabilities are found. To fail the job, parse the output with a grep or PowerShell step, or use a wrapper tool, and group related Microsoft.* package updates in Dependabot.

GitHub Actions vs Azure DevOps Pipelines for .NET CI?

Both support the same dotnet CLI quality gates. GitHub Actions uses actions/setup-dotnet with global.json, while Azure DevOps uses the UseDotNet@2 task and PublishTestResults@2 for trx reports. Choose based on where your repositories and organizational tooling already live.

Why is my .NET CI pipeline slow and how do I fix it?

Slow pipelines usually come from redundant restores and serial jobs. Cache NuGet packages, split format, build, and test into parallel jobs, pass --no-restore and --no-build between steps, shard tests with dotnet test --filter, and move slow integration tests to a nightly schedule.

How do I roll back a failed Azure App Service deployment?

Use a manual workflow_dispatch pipeline that runs az webapp deployment slot swap to promote a last-known-good slot back to production. For EF Core schema changes, pair the rollback with a migration-down step or design migrations using the expand-contract pattern.