stylecop-analyzers
stylecop-analyzers sets up the StyleCop.Analyzers package in .NET repositories, establishing clear ownership between root .editorconfig and stylecop.json configuration. It detects existing state, adds the package where needed, and prevents rule overlap with other analyzer packs. Use it when your team requires stronger style conventions than SDK analyzers alone provide.
stylecop-analyzers adds StyleCop.Analyzers to .NET projects to enforce naming, layout, and documentation style rules.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
stylecop-analyzers adds StyleCop.Analyzers to .NET projects to enforce naming, layout, and documentation style rules. stylecop-analyzers sets up the StyleCop.Analyzers package in .NET repositories, establishing clear ownership between root .editorconfig and stylecop.json configuration. It detects existing state, adds the package where needed, and prevents rule overlap with other analyzer packs. Use it when your team requires stronger style conventions than SDK analyzers alone provide.
Use it when
- stylecop-analyzers establishes clear ownership between your root .editorconfig and stylecop.json files.
- stylecop-analyzers integrates StyleCop.Analyzers with existing .NET SDK analyzers to prevent rule overlap.
Verify before relying
Read SKILL.md below before installing (5 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/stylecop-analyzers · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I add stylecop to my C# project?
stylecop-analyzers automates adding the StyleCop.Analyzers package to your .NET project. The skill detects your current setup, installs the NuGet package where needed, and configures it to work alongside existing .NET SDK analyzers without rule duplication. Once added, StyleCop enforces naming, layout, and documentation rules across your codebase.
What is the stylecop.json configuration guide?
stylecop-analyzers establishes clear ownership between your root .editorconfig and stylecop.json files. The skill sets up stylecop.json to define stricter code style conventions for your team, while .editorconfig handles broader formatting. stylecop-analyzers bootstraps both files if missing from your repository and ensures they work together without conflicting rule definitions.
How does stylecop-analyzers compare to SDK analyzers?
stylecop-analyzers integrates StyleCop.Analyzers with existing .NET SDK analyzers to prevent rule overlap. While SDK analyzers provide baseline code quality checks, StyleCop.Analyzers enforces stricter naming conventions, layout standards, and documentation requirements. stylecop-analyzers detects what you already have and adds StyleCop only where it fills gaps your team needs.
Can I enforce naming conventions with stylecop-analyzers?
Yes. stylecop-analyzers configures StyleCop.Analyzers to enforce naming, layout, and documentation rules tailored to your team's standards. The skill sets up stylecop.json with your preferred naming conventions and integrates them into your build process so violations are caught automatically during compilation.
What happens if stylecop.json is missing from my repository?
stylecop-analyzers detects when stylecop.json is absent and bootstraps a default configuration for you. It also ensures your .editorconfig is properly set up to work with StyleCop.Analyzers. This lets your team start enforcing consistent code style immediately without manual configuration from scratch.
How do I set up stylecop-analyzers for my team?
stylecop-analyzers handles the full setup: it adds the StyleCop.Analyzers NuGet package, creates or updates stylecop.json with team conventions, and configures .editorconfig for consistent enforcement. The skill validates your setup and can run verification checks on build to ensure all team members follow the same style rules.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
StyleCop Analyzers
Trigger On
- the repo wants
StyleCop.Analyzers - naming, layout, or documentation style needs stronger enforcement
- the team needs
stylecop.jsonguidance
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
(truncated - see the full file via the links below)
File tree — 5 files
catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers/SKILL.md
catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers/manifest.json
catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers/references/config.md
catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers/references/rules.md
catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers/references/stylecop-analyzers.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Add and configure StyleCop.Analyzers package to enforce naming, layout, and documentation rules”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Roslynator equips .NET projects with open-source static analysis and code-cleanup capabilities through NuGet analyzer packages and an optional command-line tool. Configure rule severity in `.editorconfig`, run analysis and fix workflows, or detect unused code—all while respecting your repo's existing analyzer setup.
This skill installs and configures Meziantou.Analyzer, a comprehensive rule set for .NET codebases covering design, usage, security, performance, and style concerns. It manages package setup, severity configuration in `.editorconfig`, and avoids duplication with SDK or Roslynator analyzers. Use it when your team wants broader diagnostic coverage without managing multiple analyzer packages.
This skill sets up the .NET SDK's built-in Roslyn analyzers and establishes a phased strategy for treating warnings as errors. It handles both new projects (immediate enforcement) and legacy codebases (batch-by-batch promotion), ensuring your CI fails on analyzer violations without overwhelming your team. Security rules are always prioritized.
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.
complexity sets up .NET's built-in maintainability analyzers to enforce cyclomatic complexity and coupling limits across your codebase. It configures CA1502, CA1505, and CA1506 rules in .editorconfig and CodeMetricsConfig.txt, then validates thresholds through the build pipeline.
format configures the SDK-provided dotnet format tool for .NET projects, enabling reproducible code formatting and analyzer fixes across local and CI environments. It respects .editorconfig as the source of truth for style preferences and helps avoid formatter conflicts by clarifying ownership when multiple tools are in use.
More skills csharpier (MIT) · resharper-clt (MIT)