dotnet-skills
Tool .NET Quality v1.0.0

ReSharper Command Line Tools

Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. Use when a repo wants powerful `jb inspectcode` inspections, `jb cleanupcode` cleanup profiles, solution-level `.DotSettings` enforcement, or a stronger CLI quality gate for C# than the default SDK analyzers alone.

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

Workflow

  1. Prefer solution-level runs when possible so ReSharper can resolve references and apply full inspections.
  2. Build the solution before jb cleanupcode when working at solution scope.
  3. Use jb inspectcode first to surface issues before editing anything broad.
  4. Treat surfaced issues as mandatory fixes when this gate is enabled for the repo; do not just dump a report and stop.
  5. Use jb cleanupcode with an explicit cleanup profile:

- Built-in: Full Cleanup - Built-in: Reformat Code - Built-in: Reformat & Apply Syntax Style - or a checked-in custom profile

  1. Keep durable ReSharper settings in the team-shared solution layer and commit the solution .DotSettings file when policy changes.
  2. Re-run jb inspectcode after cleanup or fixes, then run the repo's normal quality pass and tests.

Deliver

  • explicit jb inspectcode and jb cleanupcode commands
  • durable ReSharper settings in shared solution config
  • a quality gate that surfaces issues which are then fixed, not ignored

Validate

  • the target solution or project builds before solution-wide cleanup
  • jb inspectcode output is reviewed and acted on
  • cleanup profiles and shared settings are explicit
  • tests and the wider quality pass still run after ReSharper-driven fixes

Load References

  • references/resharper-clt.md
  • references/commands.md
  • references/config.md

Related skills