mcaf-dotnet-csharpier

MCAF: .NET CSharpier

Trigger On

• the repo uses or wants CSharpier
• the team prefers an opinionated formatter over many configurable style knobs

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 already standardized on dotnet format as the only formatter

Inputs

• the nearest AGENTS.md
• current formatting ownership model
• any .csharpierignore or .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. Decide whether CSharpier is the primary formatter or only complements other tools.
2. Use check mode in CI.
3. Keep ignore files and config explicit in repo.
4. Do not let CSharpier and dotnet format both own the same formatting space without documentation.

Bootstrap When Missing

If CSharpier is not configured yet:

1. Detect current state:
   • rg --files -g '.config/dotnet-tools.json' -g '.csharpierignore'
   • dotnet tool list --local
   • dotnet tool list --global
2. Prefer local tool installation for reproducible CI:
   • dotnet new tool-manifest (if missing)
   • dotnet tool install csharpier
3. Add .csharpierignore when needed and define ownership vs dotnet format in AGENTS.md.
4. Add dotnet csharpier check . to CI.
5. Run dotnet csharpier check . and return status: configured or status: improved.
6. If the repo intentionally uses only dotnet format, return status: not_applicable unless migration is requested.

Deliver

• explicit CSharpier ownership and commands
• CI-safe formatter checks

Validate

• formatter ownership is not ambiguous
• the repo is comfortable with opinionated formatting decisions