Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: `jb inspectcode`; `jb cleanupcode`; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally standardizes on another formatter. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
SkillScore68Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 10 of 15 test cases with the skill, and 8 of 15 without it.
Without skill50%
With skill68%
Checks it passed that the model alone missed
Returns status as not_applicable.
Re-runs jb inspectcode to verify fixes.
Executes project tests after code cleanup.
and 2 more in the full report
4 fixed11 passed either way7 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+73%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/19/2026v115 of 22 cases passed with skill · 15 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Our C# repository `Analytics.sln` explicitly uses CSharpier in `.config/dotnet-tools.json` and project governance strictly forbids JetBrains `.DotSettings` or ReSharper CLI gates in CI. We were asked to check if ReSharper CLT should be configured. Return your result using status, plan, actions_taken, validation_skills, verification, and remaining.
What was checked, without and with the skill
Checked
Without skill
With skill
Returns status as not_applicable.
Missed
Passed
Declines installing ReSharper CLT due to repo policy.
Passed
Passed
case-09 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md125 lines4 files
ReSharper Command Line Tools
Trigger On
the repo uses or wants ReSharper Command Line Tools
the team wants jb inspectcode or jb cleanupcode
the user asks for stronger C# inspections, cleanup profiles, or ReSharper-based CI gates
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
replacing tests with inspection output
ad-hoc formatting-only work when the repo intentionally standardizes on another formatter
repos that do not want JetBrains settings or CLT-based gates in their workflow
Inputs
the nearest AGENTS.md
the target .sln, .csproj, or bounded file set
repo-root .editorconfig
solution shared settings such as YourSolution.sln.DotSettings
Quick Start
Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.
Workflow
Prefer solution-level runs when possible so ReSharper can resolve references and apply full inspections.
Build the solution before jb cleanupcode when working at solution scope.
Use jb inspectcode first to surface issues before editing anything broad.
Treat surfaced issues as mandatory fixes when this gate is enabled for the repo; do not just dump a report and stop.
Use jb cleanupcode with an explicit cleanup profile: