What problem does it solve? Legacy .NET codebases often have hundreds of analyzer warnings, making it impossible to enable TreatWarningsAsErrors in one step. This Skill sets up first-party .NET SDK analyzers and applies a phased warning promotion strategy so CI can fail on analyzer violations without flooding the build. ## Core Features & Use Cases - Analyzer Bootstrap: Detects existing analyzer policy and configures EnableNETAnalyzers, AnalysisLevel, and AnalysisMode in Directory.Build.props. - Gradual Warning Promotion: Promotes warnings in batches (trivial hygiene, code quality, security, full coverage) using WarningsAsErrors and .editorconfig severity rules. - Policy Protection: Enforces hard rules that prevent agents from disabling TreatWarningsAsErrors, adding NoWarn suppressions, or downgrading severities to make builds pass. - Use Case: A team inherits a legacy .NET solution with 500 warnings. The Skill counts warnings by ID, asks which batch to fix first, promotes those IDs to errors, and repeats until the build is clean. ## Quick Start Ask the agent to enable built-in .NET analyzers and gradually promote Roslyn warnings to errors in this repository.