ci-cd

Automates .NET CI/CD workflows for GitHub Actions and Azure DevOps via YAML pipelines.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill ci-cd-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/ci-cd
Command: npx skills add https://github.com/Resgrid/Core --skill ci-cd-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI/CD pipelines help teams avoid slow, inconsistent releases by automating build, test, and deployment steps directly from version control.

Core Features & Use Cases

  • Pipeline as code: Enforce YAML-defined workflows in the repo so releases are reproducible and reviewable.
  • Fast feedback with quality gates: Run restore, build, formatting checks, and tests on every change to catch issues early.
  • Repeatable release promotion: Build once and promote the same artifact through environments like dev, staging, and production.
  • Common scenarios: GitHub Actions or Azure DevOps for build-test workflows, Docker image publishing on tags, and NuGet package pack-and-push for library releases.

Quick Start

Use the ci-cd skill to generate a GitHub Actions or Azure DevOps YAML pipeline that builds, formats, runs tests, and publishes a deployable artifact for your .NET solution.

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

Set up GitHub Actions for .NET by defining YAML workflows that restore dependencies, build with Release configuration, run format checks, execute tests, and publish artifacts. The ci-cd skill generates these YAML pipeline stages automatically for GitHub Actions.

Can I use Azure DevOps pipelines to build and publish NuGet packages?

Yes, Azure DevOps pipelines support building .NET projects and publishing NuGet packages. You define YAML stages to pack and push packages on release signals without hardcoding secrets, automating the library release process.

What is the best way to automate .NET testing in CI/CD pipelines?

Automate .NET testing in CI/CD by configuring YAML pipeline stages to execute tests with configurable connection settings after building with Release configuration. This catches issues early by running tests on every code change before publishing artifacts.

Does this CI/CD approach support Docker image publishing on tagged releases?

Yes, the CI/CD approach supports Docker image publishing triggered by tagged releases. You define YAML workflows in GitHub Actions or Azure DevOps that build, test, and publish Docker images automatically when release tags are pushed.

Do I need YAML to define CI/CD workflows for .NET applications?

Yes, you need YAML to define CI/CD workflows for .NET applications. Enforcing pipeline-as-code with YAML in your repository ensures builds, tests, and releases are reproducible, reviewable, and configurable without hardcoding secrets.

Why run format verification in a .NET build pipeline?

Run format verification in a .NET build pipeline to enforce code style consistency and catch formatting issues early. Including format checks in your YAML CI/CD workflow alongside tests ensures quality gates fail fast on non-compliant code changes.