resolve-diagnostics

Resolves IDE diagnostics at the warning or higher severity level for the given files, reformats them to the solution's code style, then runs the tests.

Input

One or more file or directory path arguments. Resolve them with ${CLAUDE_SKILL_DIR}/scripts/resolve-targets.sh <unity-project-root> <path>... — it prints the project-root-relative path of every .cs file in the solution, one per line, in the form lint_files, get_file_problems, and reformat_file expect, and reports each dropped path (docs, .meta, .asmdef, assets, files outside the solution) on stderr. Use that list as-is.

If no path argument is given, use AskUserQuestion to ask the user for the targets. Do not derive targets from git status — that would silently widen the scope beyond what was requested.

If the script exits with code 3, stop and report that — there is nothing to resolve.

Workflow

Step 1: Load the Coding Guide

1. Load the code-writing-guide skill — do not rely on automatic skill triggering. Every fix applied in Step 2 must follow it.
2. Read its resources/diagnostics-review-feedback.md before deciding any diagnostic in Step 2.

Never leave a warning-or-higher diagnostic unaddressed — each one is either fixed or explicitly suppressed per the criteria just read.

Step 2: Resolve Diagnostics

Resolve diagnostics at the warning or higher severity level, collecting them for all resolved files via lint_files rather than one file at a time. By default the tools also return suggestion- and hint-level results — those are out of scope, with one exception: a suggestion-level diagnostic related to performance (execution speed, memory allocation, boxing, etc.) should be considered for fixing too, though it never requires suppression when declined. Both lint_files and its fallback get_file_problems require Rider 2026.2 or later.

1. lint_files — pass every resolved file in one call
   • If the call errors, fall back to get_file_problems, called once per file
   • On a timedOut or more result, retry the outstanding file(s) with get_file_problems
   • If a timeout persists, use AskUserQuestion to confirm the user is running Rider 2026.2 or later before retrying further
   • Files reported as not analyzed carry into Step 5 as skipped
2. Decide each diagnostic per the criteria read in Step 1, and apply all resulting changes as a single set per file
   • When a fix is a rename (naming-convention inspections) or a symbol removal (unused-member findings), apply it via rename_refactoring / safe_delete so references are updated across the solution