mcaf-dotnet-stylecop-analyzers

MCAF: .NET StyleCopAnalyzers

Trigger On

• the repo wants StyleCop.Analyzers
• naming, layout, or documentation style needs stronger enforcement
• the team needs stylecop.json guidance

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

• repos that intentionally rely only on SDK analyzers
• repos where StyleCop overlaps too heavily with an existing style package and no consolidation is planned

Inputs

• the nearest AGENTS.md
• current .editorconfig
• any existing stylecop.json

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. Add StyleCop.Analyzers only if the repo wants its opinionated style rules.
2. Keep severity in the root .editorconfig.
3. Use stylecop.json only for StyleCop-specific behavioral options.
4. Prefer one checked-in stylecop.json per repo unless a project genuinely needs its own behavior.
5. Avoid rule duplication with SDK analyzers or other analyzer packs when possible.

Bootstrap When Missing

If StyleCop.Analyzers is not configured yet:

1. Detect current state:
   • rg -n "StyleCop\\.Analyzers|stylecop\\.json" -g '*.csproj' -g 'stylecop.json' .
2. Add package to the intended scope:
   • dotnet add PROJECT.csproj package StyleCop.Analyzers
3. Keep severity in root .editorconfig and use stylecop.json only for StyleCop-specific behavior.
4. Prevent overlap with existing analyzer packs by defining ownership.
5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
6. If the repo intentionally uses SDK analyzers only, return status: not_applicable.