From roslyn-mcp
Quick C# feedback without loading a solution. Use when: validating syntax, semantics, or running a small script; prototyping an expression; or explaining an isolated code fragment.
npx claudepluginhub darylmcd/roslyn-backed-mcp --plugin roslyn-mcpThis skill uses the workspace's default tool permissions.
You use **`analyze_snippet`** and **`evaluate_csharp`** for fast feedback when loading a full **`.sln`** is unnecessary or impossible.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
You use analyze_snippet and evaluate_csharp for fast feedback when loading a full .sln is unnecessary or impossible.
$ARGUMENTS should indicate either:
Full solution workflows live in roslyn://server/catalog. This skill is for ephemeral analysis only.
| Goal | Tool |
|---|---|
| Parse, bind, diagnostics on a fragment | analyze_snippet |
| Run a script / evaluate an expression (side effects, output) | evaluate_csharp |
| Production refactor / cross-file impact | Load workspace with workspace_load and use symbol tools |
analyze_snippet with the code and appropriate options (as exposed by the tool schema).evaluate_csharp; warn the user that scripts run in the host process trust boundary.workspace_load on the actual solution.Invoke with --explain or ask "explain this snippet" / "what does this do?". The skill produces a step-by-step semantic walkthrough instead of a pass/fail result:
analyze_snippet to bind the snippet and gather diagnostics.get_operations (if available) on the snippet to walk the IOperation tree — this yields the full semantic tree: local declarations, invocations, branches, loops, lambdas, await points.LocalReference, InvocationOperation, ConditionalAccessOperation)await, show the async flow: where the state machine suspends, what continuation happens on completion vs exception.Explain mode is read-only — it never calls evaluate_csharp. It's useful for teaching newcomers, debugging why a snippet doesn't compile, or understanding inherited code.
Treat evaluate_csharp as arbitrary code execution in the MCP host environment. Only run code the user explicitly supplied and avoid secrets in snippets. Explain mode is safe — it never executes.