Codex StyleCop Analyzers for C# Naming and Documentation Rules
Define where StyleCop rules apply in a .NET project and how they coexist with SDK analyzers. Keep severity in .editorconfig and use stylecop.json for tool-specific behavior.
中文Install in Codex
Codex with a .NET SDK project, its project files, and the existing analyzer and .editorconfig settings.
- Copy the entire pinned `.codex/skills/stylecop-analyzers/` directory to `.agents/skills/stylecop-analyzers/` in the target checkout.
- Open Codex in that checkout and invoke `$stylecop-analyzers` with the example task and desired output.
Example task
Invoke `$stylecop-analyzers` in a practice solution. Set a public-member documentation rule for one library, place severity in .editorconfig, and inspect build diagnostics.What to check
The configuration diff shows the affected project and rule severity. Build output demonstrates whether the intended diagnostics fire.
Original SKILL.md on GitHub · Updated
Frequently asked question
What belongs in .editorconfig and stylecop.json?
Use .editorconfig for rule enablement and severity. Use stylecop.json for StyleCop-specific behavior settings when needed.