ReSharper Inspect Code
resharper_inspectRead-onlyIdempotent
Run ReSharper static analysis to find code issues in your solution, with configurable file scope, severity, and report output.
Instructions
Run ReSharper static analysis on the solution and return the code issues it finds.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | Ant-style globs scoping the analysis to specific files, for example src/**/*.cs. Each is relative to the solution root, or absolute. jb matches them against the files that belong to a project in the solution, so one that is on disk but in no project matches nothing. An element joining several paths with ; or , is split into separate paths. | |
| detail | No | Cap on the detail the response carries: Full, the default, lists every issue on its own line, and Minimal is one line of totals. Rendering starts at this level and never goes above it, but still steps below it when the result does not fit the output budget. The DETAIL REDUCED note says which of the two happened. Response shaping only: the same analysis runs whatever the level, so a lower level does not make a call finish sooner. Pair detail=Minimal with report=Markdown for a cheap verdict in the response and every finding in the file. | Full |
| report | No | Write the complete itemised findings to a file, and name it in the response. Markdown lists every issue with its own message, which is what the response listing collapses once a solution-wide run exceeds the output budget. The file lands in a directory this server owns and is pruned after 7 days; the response carries the summary either way. | None |
| severity | No | Minimum severity to report. Error is ReSharper's compilation-error level, not a tier of high-priority warnings; raising to it usually reports nothing. | Warning |
| solutionPath | No | Path to the .sln/.slnx to run against. Overrides JB_SOLUTION_PATH and working-directory discovery. |