dotnet-quality-ci

Configure .NET code-quality gates for CI pipelines.

466|35|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-quality-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-quality-ci
Source: https://github.com/managedcode/dotnet-skills/tree/main/skills/dotnet-quality-ci
Command: npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-quality-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes and refines robust code quality gates for .NET projects within Continuous Integration pipelines, ensuring code adheres to high standards of formatting, analysis, and testing.

Core Features & Use Cases

  • CI Quality Stack Setup: Configure essential quality gates including code formatting, .editorconfig, SDK analyzers, third-party analyzers, code coverage, and security scanning.
  • Workflow Integration: Update AGENTS.md, CI workflows, and configuration files to reflect the chosen quality stack.
  • Use Case: A .NET open-source project needs to implement automated checks for code style, potential bugs, and test coverage in its GitHub Actions workflow to maintain code health and prevent regressions.

Quick Start

Use the dotnet-quality-ci skill to define the best OSS CI stack for this .NET repo.

Frequently Asked Questions about dotnet-quality-ci

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

FAQPage Schema
How do I set up code quality gates for a .NET project in CI?

To set up .NET code quality gates in CI, configure formatting, .editorconfig, SDK analyzers, third-party analyzers, code coverage, and security scanning within your GitHub Actions workflow.

What is included in a .NET CI quality stack?

A .NET CI quality stack includes code formatting, .editorconfig, SDK analyzers, third-party analyzers, code coverage, mutation testing, architecture tests, and security scanning to maintain code health.

Can I use .editorconfig and analyzer references to enforce code style in .NET pipelines?

Yes, you can enforce code style in .NET pipelines by configuring .editorconfig and adding analyzer package references to Directory.Build.props to ensure CI checks maintain formatting standards.

What's the best way to integrate mutation testing and architecture tests into .NET workflows?

The best way to integrate mutation testing and architecture tests into .NET workflows is by updating CI workflows and configuration files to include these checks alongside standard code coverage and security scanning.

Does setting up .NET code quality gates require updating AGENTS.md?

Yes, establishing .NET code quality gates requires updating AGENTS.md, CI workflows, .editorconfig, and Directory.Build.props to reflect the chosen quality stack and ensure automated checks run properly.