Use the free first-party `dotnet format` CLI for .NET formatting and analyzer fixes. USE FOR: the repo uses dotnet format; you need a CI-safe formatting check for .NET; the repo wants .editorconfig-driven style enforcement. DO NOT USE FOR: repositories that intentionally use CSharpier as the only formatter; analyzer strategy with no formatting command change. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are
SkillScore61Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 10 of 16 test cases with the skill, and 8 of 16 without it.
Without skill48%
With skill61%
Checks it passed that the model alone missed
Includes key plan
Includes command dotnet --info
Includes status: not_applicable
and 2 more in the full report
6 fixed8 passed either way6 still failing3 broke
Pass-rate lift
+13 pp
Tokens
+27%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/19/2026v114 of 23 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Our .NET development team needs to reconfigure analyzer diagnostic suppressions in GlobalSuppressions.cs and set up warning-as-error rules in Directory.Build.props. No formatting command or whitespace pipeline check changes are required. Provide the report.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes status: not_applicable
Missed
Passed
case-06 · 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.md105 lines4 files
dotnet format
Trigger On
the repo uses dotnet format
you need a CI-safe formatting check for .NET
the repo wants .editorconfig-driven style enforcement
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
repositories that intentionally use CSharpier as the only formatter
analyzer strategy with no formatting command change
Inputs
the nearest AGENTS.md
the solution or project path
the current .editorconfig
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
Prefer the SDK-provided dotnet format command instead of inventing custom format scripts.
Start with verify mode in CI: dotnet format TARGET --verify-no-changes.
Use narrower subcommands only when the repo needs them:
whitespace
style
analyzers
Keep .editorconfig as the source of truth for style preferences.
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: `jb inspectcode`; `jb cleanupcode`; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally standardizes on another formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Close match
+18 pp pass-rate lift
Generate wrapper interfaces and DI registration for hard-to-test static dependencies in C#, when the abstraction does NOT exist yet. Produces IFileSystem, IEnvironmentProvider, IConsole, IProcessRunner wrappers, or guides first-time adoption of TimeProvider and IHttpClientFactory and registering them in DI. USE FOR: generate wrapper for static, create IFileSystem wrapper, wrap DateTime.Now, make static testable, make class testable, create abstraction for File.*, generate DI registration, set up