ci-cd

Name: ci-cd
Availability: InStock
Author: Trossitec

Generate GitHub Actions and Azure DevOps YAML pipelines for .NET projects.

1|Updated Apr 28, 2026

Search Tags:#testing #ci/cd #github actions #docker #dotnet #pipelines #azure devops

Ready to run

npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill ci-cd-trossitec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-cd
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/ci-cd
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill ci-cd-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces build breakages and slow releases by guiding you to set up consistent CI/CD pipelines that compile, validate, and deploy .NET code automatically.

Core Features & Use Cases

Pipeline as code: Generate repository-tracked GitHub Actions and Azure DevOps YAML workflows to avoid click-ops and configuration drift.
Fast, trustworthy feedback loops: Add restore, build, format verification, and test stages that fail fast on every push and pull request.
Safe release workflows: Publish artifacts, container images, and NuGet packages with clear release/tag-driven stages while preventing secret leakage.

Quick Start

Ask an AI to generate a GitHub Actions CI workflow for your .NET repository that restores, builds, runs dotnet format verification, runs dotnet tests with a real service configuration, and uploads test results.

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 CI workflow for my .NET repository?▼

To set up a .NET CI workflow in GitHub Actions, you need a YAML pipeline-as-code structure with restore, build, dotnet format verification, and test stages that fail fast on every push and pull request. This ensures consistent builds and uploads test results automatically.

What is the best way to automate NuGet package publishing and Docker image builds in Azure DevOps?▼

Automating NuGet package publishing and Docker image builds in Azure DevOps requires repository-tracked YAML workflows with clear release/tag-driven stages. This pipeline-as-code approach prevents configuration drift and ensures safe releases without secret leakage.

Does this CI/CD pipeline approach support both GitHub Actions and Azure DevOps for .NET projects?▼

Yes, this CI/CD pipeline approach supports both GitHub Actions and Azure DevOps for .NET projects. It generates repository-tracked YAML workflows for both platforms to automate continuous integration, pull request validation, and environment promotion principles.

How do I prevent secret leakage when publishing .NET artifacts in continuous delivery pipelines?▼

To prevent secret leakage when publishing .NET artifacts in continuous delivery pipelines, use secret-safe configuration within your YAML workflows. Implementing clear release/tag-driven stages for artifact publishing and container images ensures credentials remain protected during environment promotion.

Why should I use pipeline-as-code YAML workflows instead of click-ops for .NET continuous integration?▼

You should use pipeline-as-code YAML workflows for .NET continuous integration to avoid click-ops and configuration drift. Tracking YAML pipelines in your repository ensures consistent build-test-format gates, enables caching for fast feedback, and maintains reliable environment promotion principles.