Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. USE FOR: .NET quality gates in CI; analyzer, coverage, mutation, and architecture-test choices; standardizing `.editorconfig`, `dotnet format`, and warning policy. DO NOT USE FOR: non-.NET repositories; generic CI/CD guidance with no .NET quality stack decisions. INVOKES: inspect the repository conte
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/19/2026
What it changes
Passed 16 of 19 test cases with the skill, and 15 of 19 without it.
Without skill77%
With skill86%
Checks it passed that the model alone missed
The response indicates that .NET quality CI guidelines do not govern Python repositories.
The response clarifies that .NET CI quality skills do not apply to generic deployment pipelines.
The response defaults to open-source and free tools and requires documenting any licensing or hosting caveats explicitly before adopting them.
3 fixed16 passed either way2 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+56%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/19/2026v119 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
When introducing third-party static analysis or dependency scanning tools to a default .NET CI quality stack, what rule governs paid or commercial tooling selection?
What was checked, without and with the skill
Checked
Without skill
With skill
The response defaults to open-source and free tools and requires documenting any licensing or hosting caveats explicitly before adopting them.
Missed
Passed
case-13 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md148 lines5 files
.NET Quality CI
Trigger On
adding or tightening .NET code-quality gates in CI
choosing analyzers, coverage, mutation, or architecture-test tooling for a .NET repo
standardizing .editorconfig, dotnet format, and warning policy
Value
produce a concrete project delta: code, docs, config, tests, CI, or review artifact
reduce ambiguity through explicit planning, verification, and final validation skills
leave reusable project context so future tasks are faster and safer
Do Not Use For
non-.NET repositories
generic CI/CD guidance with no .NET quality stack decisions
framework-specific test authoring with no quality-gate change
Inputs
the nearest AGENTS.md
the current repo-root .editorconfig and MSBuild props
the current CI workflow and package references
the active test runner model: VSTest or Microsoft.Testing.Platform
Quick Start
Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.
Workflow
Start with the repo-native baseline:
repo-root .editorconfig
dotnet format --verify-no-changes
SDK analyzers with explicit EnableNETAnalyzers, AnalysisLevel, and warning policy
Add third-party analyzers only where they close a real gap:
Use the open-source CodeQL ecosystem for .NET security analysis. Use when a repo needs CodeQL query packs, CLI-based analysis on open source codebases, or GitHub Action setup with explicit licensing caveats. USE FOR: the repo uses or wants CodeQL for .NET security analysis; GitHub code scanning is part of the CI plan. DO NOT USE FOR: teams that need a tool with no private-repo licensing caveat. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or v
Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.