skills.rest
Postpartum-genushyacinthus29
Postpartum-genushyacinthus29COMMUNITY
Explore all skills by this author →
GitHub

dotnet-format

Apply dotnet format to fix or verify code style in .NET repositories.

8|Updated Mar 29, 2026
Search Tags:#dotnet#code-quality#ci#code-formatting#editorconfig#dotnet-format
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-format-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-format
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-format
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-format-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates and enforces consistent formatting across .NET projects by using the official dotnet format tool, reducing CI failures due to formatting drift and style inconsistencies.

Core Features & Use Cases

  • SDK-driven formatting: applies dotnet format to SDK-style repos and projects to standardize code.
  • CI-friendly checks: supports verify-no-changes to gate PRs and CI pipelines.
  • EditorConfig-driven style: respects repo .editorconfig rules for consistent code style.

Quick Start

Run dotnet format on your solution or project to apply formatting changes and verify no changes are needed in CI.

Frequently Asked Questions about dotnet-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce .NET code formatting in CI pipelines?▼

To enforce .NET code formatting in CI pipelines, use the dotnet format tool with the verify-no-changes check to gate pull requests and prevent style inconsistencies. It applies EditorConfig rules to SDK-based projects.

How does EditorConfig-driven code style verification work for .NET repositories?▼

EditorConfig-driven code style verification works by applying the dotnet format tool to .NET repositories, reading your .editorconfig rules to automatically fix or verify code style and formatting across solutions and projects.

Do I need the .NET SDK installed to run dotnet format on my projects?▼

Yes, you need the .NET SDK installed in your environment to run dotnet format. The tool targets SDK-based projects and requires the SDK to apply formatting changes and verify code style.

What is the best way to verify code style without applying changes in CI?▼

The best way to verify code style without applying changes in CI is using dotnet format with the verify-no-changes check. This gates PRs by failing the pipeline if formatting drift is detected, ensuring consistent code style.

Why does my .NET formatting check fail in CI despite local formatting?▼

Your .NET formatting check fails in CI due to formatting drift and style inconsistencies. Using dotnet format with verify-no-changes and repo EditorConfig rules ensures local and CI environments apply identical code style standards.

Can I apply dotnet format to an entire solution or individual projects?▼

Yes, you can apply dotnet format to an entire solution or individual projects. The tool targets SDK-based projects and follows repository guidance to apply EditorConfig-driven style and formatting across the specified scope.

Related Skills

Explore More Software Engineering Skills→
managedcodemanagedcode
466

dotnet-analyzer-config

Create a repository-wide .editorconfig file configuring .NET analyzer and style rules.

Official
Intermediate
jasonkuhrtjasonkuhrt
1

review:gate

Run gate-tier code review checks for type correctness, lint results, and CI status.

Community
Basic
DalimovichDalimovich

github-code-review

Coordinate multi-agent AI reviews on GitHub pull requests.

Community
Advanced
managedcodemanagedcode
4

mcaf-dotnet-format

Apply `dotnet format` to format .NET code and enforce `.editorconfig` style rules.

Official
Intermediate