Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects.
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 15 of 19 test cases with the skill, and 8 of 19 without it.
Without skill41%
With skill77%
Checks it passed that the model alone missed
returns status: improved
returns status: configured
returns status: not_applicable
and 8 more in the full report
9 fixed8 passed either way4 still failing1 broke
Pass-rate lift
+36 pp
Tokens
+12%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/19/2026v117 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
In the structured result format for an analyzer configuration task, how should unresolved items or remaining tasks be represented when all changes were completed with zero issues?
What was checked, without and with the skill
Checked
Without skill
With skill
sets remaining field to none when no unresolved items exist
Missed
Passed
case-18 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md101 lines4 files
StyleCop Analyzers
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
Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.
Workflow
Add StyleCop.Analyzers only if the repo wants its opinionated style rules.
Keep severity in the root .editorconfig.
Use stylecop.json only for StyleCop-specific behavioral options.
Prefer one checked-in stylecop.json per repo unless a project genuinely needs its own behavior.
Avoid rule duplication with SDK analyzers or other analyzer packs when possible.