What problem does it solve? .NET teams often need broader static analysis than the built-in SDK analyzers provide, but adding Roslynator without a plan causes rule conflicts with StyleCop, Meziantou, or dotnet format. This Skill guides the deliberate adoption of Roslynator analyzer packages and its optional CLI with clear rule ownership and reproducible commands. ## Core Features & Use Cases - Analyzer Package Setup: Detect existing analyzer state, install Roslynator.Analyzers via NuGet, and configure rule severity in .editorconfig. - CLI Workflows: Adopt the Roslynator CLI for analyze, fix, find-unused, and format flows with bounded, rebuild-verified auto-fixes. - Rule Ownership Planning: Avoid duplicate diagnostics across analyzer packs by assigning severity ownership in .editorconfig. - Use Case: A team wants to find unused code before a release. The Skill bootstraps the CLI, runs roslynator find-unused on the solution, and returns a structured status report with verification evidence. ## Quick Start Ask the assistant to add Roslynator analyzers to your .NET solution and configure rule severity in the root .editorconfig.