dotnet-format

Check the C# files changed on the current branch with the .NET SDK's dotnet format, or the dotnet-format global tool for a .sln holding a project that is not SDK-style (whitespace, code-style, and analyzer rules the repository configures), and with this skill's region layout checker, then offer to fix what they find. Every step is one script command, run exactly as shown. Each prints one tab-separated fact per line. Do not read the changed files, count braces, or edit source files yourself: the tools find and fix every violation. Act on the printed lines, not the exit code: a command that reports findings also exits 1. Report each REFUSED <path> <reason> line: the script left that path, outside the repository, behind a link, or read-only, unread or unwritten. A last line FAILED <reason> means stop: Read the end of the LOG file, when one was printed, and report the reason, the cause the log shows, and its path.

Steps

1. Resolve the targets from the directory the user invoked the skill in:

   {{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/dotnet_format_targets.py" resolve

   STOP <reason> means there is nothing to format: report the reason and stop. Report a FETCH_FAILED <reason> line (the base is origin as last fetched, so it may be stale) and go on. Report each SKIPPED_ASPNET <file> <project> line (the solution is formatted with the global tool, which the skill does not run on ASP.NET projects) and each OUTSIDE_SOLUTION <file> line (no project of the chosen solution owns it); the formatter skips both, and only the layout checker sees them. Keep the path from the REPO_ROOT <path> line, the solution from the SOLUTION <solution> <score> line (the score counts the changed files its projects own and is not passed on), and the path from the FILE_LIST <path> line as <REPO_ROOT>, <SOLUTION>, and <FILE_LIST> in the next steps.

2. Check the layout analyzer configuration:

   {{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/csharp_layout.py" config --repo-root "<REPO_ROOT>" --solution "<SOLUTION>" --file-list "<FILE_LIST>"

   The command evaluates each project that owns a changed file with MSBuild (dotnet msbuild -getItem), which follows the project's imports and may resolve its SDK, as step 3's formatter does when it loads the solution, so it runs nothing a dotnet format of the same solution would not. Each setting is judged as the changed files see it, so path-specific sections and .globalconfig values count. If any SETTING line says missing, list those settings and call AskUserQuestion with Add settings / Skip. On Add settings, rerun the command with --apply and report its ADDED lines, and each UNREADABLE <.editorconfig> <reason> line, an .editorconfig it added nothing to, so its settings are still missing; it adds the missing settings as the first section of the outermost .editorconfig, so every existing section still overrides them. A SETTING state of other:<value> is the repository's own choice: report it, never change it. If PACKAGE Roslynator.Formatting.Analyzers missing, tell the user the RCS* layout rules run only once the solution references that NuGet package (for example a PackageReference with PrivateAssets="all" in Directory.Build.props, followed by a restore or build, since the formatter runs with --no-restore). If PACKAGE Roslynator.Formatting.Analyzers unknown <reason>, report the reason: whether the RCS* rules run could not be told. Never add the package yourself.

3. Check. Run both commands from step 1's values, giving the formatter run a 600000 ms timeout:

   {{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/run_dotnet_format.py" check --repo-root "<REPO_ROOT>" --solution "<SOLUTION>" --include-file "<FILE_LIST>"
   {{PYTHON}} -B "${CLAUDE_SKILL_DIR}/scripts/csharp_layout.py" check --repo-root "<REPO_ROOT>" --file-list "<FILE_LIST>"

   Each prints DIAGNOSTIC or VIOLATION lines and a SUMMARY <count> <files> <rules> line; the formatter also prints LOG <path> with its full output when it ran. Report each UNREADABLE <file> <reason> line: the layout checker left that file unchecked and unfixed.

4. If both summaries count 0 and neither command printed a REFUSED or UNREADABLE line, report "no formatting issues found on changed files" and stop. When both count 0 but a line was REFUSED or UNREADABLE, report that no issues were found in the files checked, name the files left unchecked, and stop. Otherwise report the counts, files, and distinct rules, and call AskUserQuestion with Fix / Skip. region-scope violations are report-only: tell the user which #endregion to move into the scope where its #region opened.
5. If Fix, run the step 3 formatter command with fix in place of check (same timeout) and the layout command with --fix added, then rerun both step 3 commands once to re-verify. If the formatter's fix ends FAILED, report its SAVED <file> lines (fixes already in the working tree) and its UNFINISHED <file> lines (fixes not saved) with the reason, and stop. If the layout fix ends FAILED, report its FIXED lines before that line (fixes already in the working tree), the reason, and that the files after them are unfixed, and stop. Report what remains, with the LOG path if the formatter still reports diagnostics; do not loop.

Important

• Do not stage or commit fixed files; leave them in the working tree for the developer to review.