{"enrichment":{"faq":[{"a":"analyzer-config establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds.","q":"What does analyzer-config do for .NET projects?"},{"a":"analyzer-config helps you create or normalize a root .editorconfig to centralize .NET analyzer and style rule configuration. It guides you through structuring rule ownership, detecting conflicts, and establishing a single source of truth for team coding standards across your repository.","q":"How do I set up a root editorconfig for a .NET repo?"},{"a":"analyzer-config resolves conflicting or unclear analyzer severity and code-style ownership across a .NET repository by normalizing your .editorconfig structure. It identifies competing rule definitions and consolidates them into a consistent, documented configuration that your entire team can follow.","q":"How can analyzer-config resolve conflicting analyzer severity?"},{"a":"Yes. analyzer-config validates that rule severity is reproducible and consistent across local and CI builds. This ensures your analyzer configuration behaves the same way whether developers run it locally or in your continuous integration pipeline.","q":"Can analyzer-config validate rule consistency in CI builds?"},{"a":"analyzer-config can bootstrap analyzer configuration when none is currently structured or documented. It provides guidance on organizing analyzer rules, managing code style rules, and establishing best practices so your repository has a clear, centralized configuration from the start.","q":"What if I have no analyzer configuration yet?"},{"a":"Yes, analyzer-config is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial projects.","q":"Is analyzer-config open source?"}],"shadow_tags":["config-as-code","rule-enforcement","code-quality-setup","dotnet-standards","static-analysis-config","team-conventions","build-consistency","linting-framework"],"summary_rewrite":"This skill establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds."},"files":[{"bytes":5116,"path":"catalog/Tools/Analyzer-Config/skills/analyzer-config/SKILL.md","sha256":"7fd74b30db8d418e97d5f34ae5d65334bf75aa1ee954363b630f750162b7404a","url":"https://skillfed.io/files/managedcode/dotnet-skills/analyzer-config/435f3247/SKILL.md"}],"id":"managedcode/dotnet-skills/analyzer-config","links":{"html":"https://skillfed.io/managedcode/dotnet-skills/analyzer-config","md":"https://skillfed.io/managedcode/dotnet-skills/analyzer-config.md","repo":"https://github.com/managedcode/dotnet-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":35,"language":"C#","last_updated":"2026-07-25","license":"MIT","name":"analyzer-config","publisher":"managedcode","stars":463},"relations":{"similar":[{"id":"managedcode/dotnet-skills/code-analysis"},{"id":"managedcode/dotnet-skills/quality-ci"},{"id":"managedcode/dotnet-skills/meziantou-analyzer"},{"id":"managedcode/dotnet-skills/roslynator"},{"id":"managedcode/dotnet-skills/complexity"},{"id":"managedcode/dotnet-skills/stylecop-analyzers"},{"id":"managedcode/dotnet-skills/format"},{"id":"managedcode/dotnet-skills/resharper-clt"},{"id":"managedcode/dotnet-skills/modern-csharp"},{"id":"managedcode/dotnet-skills/csharpier"}]},"slug":{"owner":"managedcode","repo":"dotnet-skills","skill":"analyzer-config"},"version":"435f3247"}