skills.rest
managedcode
managedcodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

mcaf-dotnet-quality-ci

Configure .NET code-quality gates for CI pipelines.

4|Updated Mar 6, 2026
Search Tags:#code quality#automation#testing#.net#ci#analyzers
One-click install
npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-quality-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcaf-dotnet-quality-ci
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-dotnet-quality-ci
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-quality-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps .NET projects establish and refine robust code quality gates within their Continuous Integration (CI) pipelines, ensuring code health and maintainability.

Core Features & Use Cases

  • CI Quality Gates: Sets up or improves formatting, code analysis, coverage, and security scanning for .NET projects.
  • Standardization: Ensures consistency in .editorconfig, CI workflows, and analyzer configurations.
  • Use Case: A .NET project needs to ensure all new code adheres to strict quality standards before merging. This Skill can be used to automatically configure and enforce rules for formatting, static analysis, and test coverage in the CI pipeline.

Quick Start

Use the mcaf-dotnet-quality-ci skill to set up a baseline .NET code quality CI stack for this repository.

Frequently Asked Questions about mcaf-dotnet-quality-ci

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

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

Setting up .NET code quality gates involves configuring formatting, .editorconfig files, SDK analyzers, and security scanning within your CI pipeline YAML to ensure all new code meets strict standards before merging.

What is included in a standard .NET CI quality stack?▼

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

Does this approach support third-party analyzers and mutation testing for .NET?▼

Configuring .NET quality gates explicitly supports adding third-party analyzers, mutation testing, and architecture tests alongside standard SDK analyzers to provide comprehensive static analysis and code validation.

How do I enforce .editorconfig formatting rules across a .NET repository?▼

You enforce .editorconfig formatting rules across a .NET repository by standardizing the configuration file and integrating it into your CI workflows, ensuring consistent code style and static analysis behavior during automated pipeline execution.

When do I need to configure explicit quality gates for a .NET project?▼

You need to configure explicit .NET quality gates when a repository requires strict adherence to formatting, static analysis, and coverage standards before code merges, utilizing pipeline YAML and AGENTS.md documentation to define the stack.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

greenfield-baseline

Automate project scaffolding with quality gates, CI/CD, and repository structure.

Community
Advanced
gab3mionigab3mioni

laravel-static-analysis

Automate Laravel 12 static analysis, formatting, and refactoring with Pint, Larastan, Rector, and Pest.

Community
Advanced
Avila-TekAvila-Tek

ci-cd-and-automation

Automate CI/CD quality gates with lint, type-check, tests, and builds.

Official
Advanced
ClearMeasureLabsClearMeasureLabs
3

roslynator-analysis

Execute Roslynator static analysis on .NET solutions and summarize code quality diagnostics.

Official
Advanced