Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From glidermcp
Provides semantic navigation, diagnostics, reference resolution, call graphs, impact analysis, and safe refactoring for C#/.NET repositories via GliderMCP.
npx claudepluginhub glidermcp/glidermcp.com --plugin glidermcpHow this skill is triggered — by the user, by Claude, or both
Slash command
/glidermcp:glider-csharpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use GliderMCP when working in a C# or .NET repository and the task needs semantic facts rather than plain text search.
Performs structured code reviews for .NET projects using Roslyn MCP tools, covering correctness, security, performance, architecture compliance, and test coverage.
Runs Roslynator CLI for C# static analysis, auto-fixes diagnostics, formats code, detects unused code, and enforces standards in .NET projects. Use for linting, cleanup, or quality tasks.
Rename and refactor C# symbols in a .NET solution or multi-solution monorepo with a one-shot Roslyn CLI. Use when the user asks to rename a symbol, preview impact, update references across a solution, or refactor shared projects across several solutions.
Share bugs, ideas, or general feedback.
Use GliderMCP when working in a C# or .NET repository and the task needs semantic facts rather than plain text search.
Start by checking server_status. If no workspace is loaded, call load with the relevant .sln, .slnx, or .csproj. Prefer find_code as the front door when the user asks to locate behavior by intent. Use search_symbols, resolve_symbol, or get_symbol_at_position before symbol-specific tools, and treat returned symbolKey values as opaque stable identities.
For edits, gather evidence first with tools such as find_references, find_implementations, find_callers, get_outgoing_calls, analyze_change_impact, get_cascade_impact, get_diagnostics, and diagnostic_hotspots. Prefer preview-first refactoring tools where available. After external edits, use sync for changed .cs files and reload for structural project changes.
Use shell text search only for non-C# assets, literal strings, config files, or when a semantic tool cannot answer the question.