ci-cd

Automate .NET build, test, and deployment pipelines with GitHub Actions or Azure DevOps.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill ci-cd-codewithmukesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/ci-cd
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill ci-cd-codewithmukesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide repeatable, repository-driven CI/CD workflows that deliver fast feedback, enforce quality gates, and reliably promote the same build artifact through environments so teams avoid flaky deployments and environment-specific builds.

Core Features & Use Cases

  • GitHub Actions and Azure DevOps templates for build, test, and publish stages tailored to .NET projects.
  • Build once, deploy many workflows that produce a single artifact for promotion across dev, staging, and production.
  • Test and format gating to ensure code style and automated tests pass before deployment, plus examples for publishing Docker images and NuGet packages and integrating services like Postgres for test runs.
  • Security and best practices including use of pipeline secrets, avoiding hardcoded credentials, caching NuGet, and tagging-driven releases.
  • Decision guidance for choosing between GitHub Actions (OSS) and Azure DevOps (enterprise), and tactics for database migrations and environment promotion.

Quick Start

Create a GitHub Actions workflow that restores, builds, formats, tests on push, and publishes a Docker image when creating a release tag.

Frequently Asked Questions about ci-cd

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

FAQPage Schema
How do I set up a CI/CD pipeline for a .NET application using GitHub Actions?

To set up a .NET CI/CD pipeline using GitHub Actions, you create repository-driven workflows that restore, build, format, test on push, and publish Docker images or NuGet packages when creating release tags. This provides fast feedback and automates deployments.

What is the build once, deploy many pattern for .NET releases?

The build once, deploy many pattern produces a single build artifact that is promoted across dev, staging, and production environments. This avoids environment-specific builds and flaky deployments by ensuring the exact same artifact is reliably promoted through your pipeline.

Should I choose GitHub Actions or Azure DevOps for my .NET CI/CD workflows?

Choose GitHub Actions for open source projects or Azure DevOps for enterprise scenarios. Both provide tailored templates for .NET build, test, and publish stages, with decision guidance available to help you select based on your specific project scale and requirements.

Can I publish Docker images and NuGet packages automatically on git tags?

Yes, you can publish Docker images and NuGet packages automatically using tagging-driven releases. Your .NET CI/CD workflow triggers the publish stage to push artifacts to container registries or NuGet when a release tag is created.

How do I handle database migrations and secure secrets in Azure DevOps pipelines?

Handle database migrations and secure secrets in Azure DevOps by utilizing pipeline secrets to avoid hardcoded credentials. The workflows provide tactics for environment promotion and database migrations while enforcing test and format gating before deployment.