ReSharper InspectCode

Install and run JetBrains ReSharper Command Line Tools (jb inspectcode) against a .NET solution or project, defaulting to XML output and a deterministic report path. Use when you need whole-solution ReSharper-style inspection from the terminal, a machine-readable inspection report, or must analyze current C#/.NET issues without relying on Rider UI.

Keep SKILL.md lean. Read only the reference file you need:

• references/workflow-details.md for assumptions, selection rules, defaults, and failure handling.
• references/platform-commands.md for exact PowerShell and Bash command forms.
• references/implementation-examples.md for pseudocode, response patterns, and extension ideas.

Default workflow

1. Verify the .NET SDK is available with dotnet --version. Stop if it is missing.
2. Check whether jb is already on PATH with jb --version.
3. If jb is missing, try dotnet tool install -g JetBrains.ReSharper.GlobalTools. If that fails or global tools are blocked, create a local tool manifest and install the tool locally, then invoke it with dotnet tool run jb.
4. Walk upward from the current working directory to find the repository root (.git directory). Use this as the search ceiling. If no .git is found, fall back to the filesystem root.
5. Within that boundary, select the nearest *.sln. If none exists, fall back to the nearest *.csproj.
6. Create ./artifacts if needed and default the report path to ./artifacts/inspectcode-report.xml unless the user asked for another path or format.
7. Look for a *.DotSettings file next to the target. If found, pass --settings=<path>. The tool also respects .editorconfig automatically.
8. Run InspectCode with --no-build --format=Xml unless the user explicitly wants a build-backed run or another output format.
9. Return the analyzed target, the report path, and a concise severity summary parsed from the XML (see references/workflow-details.md for XML structure). State that the analysis reflects files on disk, not unsaved IDE buffers.

Operating rules

• Prefer .sln over .csproj.
• Prefer XML over JSON unless the user explicitly requests another format.
• Prefer --no-build for iterative inspection.
• Be explicit when a global tool install fails and the workflow falls back to a local tool manifest.
• Stop with a clear error if no solution or project file is found.