ci-cd

Automate .NET CI/CD pipelines for GitHub Actions and Azure DevOps.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Maj3D10/Training-Platform --skill ci-cd-maj3d10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/ci-cd
Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill ci-cd-maj3d10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines prevent broken builds and slow releases by automating build, test, publish, and deploy steps consistently for .NET projects.

Core Features & Use Cases

  • Pipeline as code: keep GitHub Actions or Azure DevOps pipeline definitions in the repository for review and repeatability.
  • Fast feedback loop: run restore, build, format checks, and tests on every push or PR to catch issues early.
  • Promote the same artifact: build once, then deploy the same output across dev → staging → production.
  • Use case: for a team maintaining a .NET service with Postgres-backed integration tests, this skill helps structure a workflow that runs tests with a real database container, publishes results, and (optionally) builds and pushes a Docker image or publishes NuGet packages.

Quick Start

Load the ci-cd skill when creating or reviewing your CI/CD workflow and use its GitHub Actions or Azure DevOps patterns as the template for your build, test, publish, and deploy stages.

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 GitHub Actions pipeline for a .NET application?

You can define a GitHub Actions pipeline for .NET by committing workflow files that automate restore, build, format checks, and tests on every push to catch issues early. This approach enforces pipeline-as-code for repeatable builds.

What is the best way to run integration tests with a Postgres database container in Azure DevOps?

Running integration tests with a Postgres database container in Azure DevOps involves structuring your pipeline to spin up the container, run tests against the real database, and publish results before promoting the build artifact.

Does this CI/CD approach support publishing NuGet packages and Docker images?

Yes, the CI/CD workflow supports publishing NuGet packages and building or pushing Docker images as part of your release flow. These steps are defined in pipeline-as-code definitions within your repository.

How do I build once and promote the same artifact across dev, staging, and production environments?

To build once and promote artifacts across environments, configure your pipeline to compile the output a single time and then deploy that same artifact to dev, staging, and production without rebuilding, ensuring consistency and avoiding skipped quality gates.

Can I use this skill to validate pull requests for my .NET service?

Yes, you can use these pipeline patterns to validate pull requests by running format checks and tests on every PR. This provides a fast feedback loop to catch issues before merging changes into the main branch.

Why should I enforce pipeline-as-code for deployment workflows instead of using manual configurations?

Enforcing pipeline-as-code for deployment workflows prevents broken builds by keeping definitions in the repository for review and repeatability. It ensures format and tests run on every change without skipping quality gates.