Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules.
CSharpier for .NET
Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model. USE FOR: the repo uses or wants CSharpier; the team prefers an opinionated formatter over many configurable style knobs. DO NOT USE FOR: repos that already standardized on dotnet format as the only formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Trigger On
- the repo uses or wants
CSharpier - the team prefers an opinionated formatter over many configurable style knobs
Workflow
- Decide whether CSharpier is the primary formatter or only complements other tools.
- Use
checkmode in CI. - Keep ignore files and config explicit in repo.
- Do not let
CSharpieranddotnet formatboth own the same formatting space without documentation.
Deliver
- explicit CSharpier ownership and commands
- CI-safe formatter checks
Validate
- formatter ownership is not ambiguous
- the repo is comfortable with opinionated formatting decisions
Load References
Related skills
Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate.
Chous
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion.
Microsoft.CodeAnalysis.NetAnalyzers