dotnet-format

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

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. Prefer the SDK-provided dotnet format command instead of inventing custom format scripts.
2. Start with verify mode in CI: dotnet format TARGET --verify-no-changes.
3. Use narrower subcommands only when the repo needs them:
   • whitespace
   • style
   • analyzers
4. Keep .editorconfig as the source of truth for style preferences.
5. If the repo also uses CSharpier, document which tool owns which file types or rules.

Bootstrap When Missing

If dotnet format is requested but not available yet:

1. Detect current state:
   • dotnet --info
   • dotnet format --version
2. Treat dotnet format as SDK-provided, not as a separate repo-local tool by default.
3. If the command is missing, install or upgrade to a supported .NET SDK, then recheck dotnet format --version.
4. Add explicit local and CI commands to AGENTS.md, usually:
   • dotnet format TARGET --verify-no-changes
5. Run the chosen command once and return status: configured or status: improved.
6. If the repo intentionally uses only CSharpier for formatting ownership, return status: not_applicable.