name: dotnet-quality-ci
version: "1.0.0"
category: "Code Quality"
description: "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 when a .NET repo needs an explicit quality stack in AGENTS.md, docs, or pipeline YAML."
compatibility: "Requires a .NET solution or project; may update AGENTS.md, CI workflows, a repo-root .editorconfig, Directory.Build.props, or analyzer package references."

.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

1. Read the nearest AGENTS.md and confirm scope and constraints.
2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

1. Start with the repo-native baseline:
2. repo-root .editorconfig
3. dotnet format --verify-no-changes
4. SDK analyzers with explicit EnableNETAnalyzers, AnalysisLevel, and warning policy
5. Add third-party analyzers only where they close a real gap:
6. StyleCopAnalyzers
7. Roslynator
8. Meziantou.Analyzer
9. framework analyzers such as xUnit, MSTest, or TUnit analyzers
10. Separate quality gates by purpose:
11. formatting and style
12. correctness and static analysis
13. coverage and reports
14. architecture rules
15. security scanning
16. mutation testing
17. For complexity, use a composite approach:
18. CA1502 thresholding
19. maintainability limits in AGENTS.md
20. architecture tests
21. coverage and mutation where risk justifies it
22. Make ownership explicit in AGENTS.md and CI:
23. which command formats
24. which command analyzes
25. which command measures coverage
26. which runner model the tests use
27. After any .NET code change, the repo's quality pass must be runnable by agents:
28. format
29. build
30. analyze
31. focused tests
32. broader tests
33. coverage and report generation when configured
34. extra configured gates only when the repo actually enabled them
35. Route tool-specific setup through dedicated skills where possible:
36. dotnet-format
37. dotnet-code-analysis
38. dotnet-analyzer-config
39. analyzer-pack skills such as dotnet-stylecop-analyzers, dotnet-roslynator, and dotnet-meziantou-analyzer
40. coverage/reporting skills such as dotnet-coverlet and dotnet-reportgenerator
41. architecture/security skills such as dotnet-netarchtest, dotnet-archunitnet, and dotnet-codeql
42. Avoid overlapping tools with conflicting ownership. If you add an opinionated formatter, define whether it replaces or complements dotnet format.

Bootstrap When Missing

If a quality gate is requested but not configured, use this activation path:

1. Detect current state in .csproj, Directory.Build.*, .editorconfig, tool manifests, and CI workflow files.
2. Choose exactly one owner command per gate category (format, analyze, test, coverage, architecture, security, mutation).
3. Install the minimal required package or tool and commit checked-in config files.
4. Wire the gate into both AGENTS.md and CI with explicit commands.
5. Run a first verify pass, fix actionable failures, and rerun.
6. Return status: configured if newly enabled and passing, or status: improved if issues remain but baseline improved.
7. Return status: not_applicable only when the gate is explicitly out of scope for this repo.

Deliver

• a documented .NET quality baseline
• CI commands that are explicit and reproducible
• analyzer and coverage choices that match the repo's runner model
• a documented post-change quality pass for agents and CI
• tool selection that stays open-source and free by default, with caveats called out explicitly

Validate

• repo-root .editorconfig is the default source of truth for per-rule severity
• formatting, analyzer, and coverage commands are runner-compatible
• added tools cover distinct gaps instead of duplicating each other
• complexity and architecture policy are explicit, not implied
• .NET code changes are expected to pass more than tests alone when quality gates are configured
• any licensing or hosting caveat is documented before the tool becomes a default gate

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

1. Plan first (mandatory):
2. analyze current state
3. define target outcome, constraints, and risks
4. write a detailed execution plan
5. list final validation skills to run at the end, with order and reason
6. Execute one planned step and produce a concrete delta.
7. Review the result and capture findings with actionable next fixes.
8. Apply fixes in small batches and rerun the relevant checks or review steps.
9. Update the plan after each iteration.
10. Repeat until outcomes are acceptable or only explicit exceptions remain.
11. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

Required Result Format

• status: complete | clean | improved | configured | not_applicable | blocked
• plan: concise plan and current iteration step
• actions_taken: concrete changes made
• validation_skills: final skills run, or skipped with reasons
• verification: commands, checks, or review evidence summary
• remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

• read references/editorconfig-and-ci.md first for ownership and config rules
• open references/quality-toolchain.md for the curated OSS tool list
• open references/workflows.md for GitHub Actions workflow examples
• open references/checklist.md for a comprehensive CI quality checklist
• use the dedicated tool skill when you are installing, configuring, or debugging one specific tool

Example Requests

• "Define the best OSS CI stack for this .NET repo."
• "Add .NET analyzers, coverage, and mutation testing guidance."
• "Make .editorconfig and CI agree in our .NET solution."